3 ms·
Except in my experience most attempts at microservices scale extremely poorly because they have nowhere near enough precision in their APIs to get just the info
by ris 5y ago
Except in my experience most attempts at microservices scale extremely poorly because they have nowhere near enough precision in their APIs to get just the information you need and so most applications end up fetching way, way more data than they need and whittling it down manually - and often having to stitch together the results from multiple calls.
That of course leads you down the path of creating an "oddly specific" API that caters exactly to the needs of the clients, down to the point that small changes in the client's needs require changes in the upstream service(s) - so your "separation of concerns" has become a joke.
- lIIIllllIIII 5y agoIs it a common thing for "proper" microservices to have microservices retrieve data from other services via APIs? I've worked on "microservices" systems before that do this. They were mostly shit. The system I'm working on at the moment has each service subscribe to events and maintain its own database. The only comms is via events. It works pretty well and everything really is nicely separated, but it feels a bit haphazard.