News for hackers. Stuff that matters.
Re:For Want of a JOIN by pwg on Thursday December 22, 2022 @09:17AM (#34093458)
> Or does every team doing microservices silently expect that one day a data team will start querying for a massive number of records-by-ID from every service, and the veterans in each team plan for this load pattern accordingly?

What tends to be by far more common is that each team fails to envision that someone, somewhere, sometime in the not so distant future will want or be required to retrieve more than one "element" at a time via their APIs. And so panic ensues when "other entity" begins feeding 20 API retrievals per second at their "one-at-a-time API" and their performance goes off the cliff it was always sitting near.

Re:For Want of a JOIN by NegativeLatency on Thursday December 22, 2022 @10:14AM (#34094082)
Extra points if you manage to do it to your own team’s APIs because of bad design and planning
Re:For Want of a JOIN by tracker1 on Thursday December 22, 2022 @10:56AM (#34094666)
You mean like 8+ joins to get that single record and then having it bottleneck when you get a few hundred requests a minute? (not bitter at all here)