[foobiekr]

Most of the real world "microservices" usage outside of FAANG has been to legitimize polyglot development (a net negative for most organizations) and the to create heretofore unseen levels of Conway's law. A microservice per person? Sure, why not?

It's madness. The solution is to avoid the polyglot issue by fiat and to ensure that there is some actual planning and rationale around when it makes sense to add a service. Most groups I've talked to don't even have a good answer to "why is this in a separate service from that?" when asked, and I've talked to a lot of them.

[blowski]

I agree. There’s a whole cohort that seems to think you should introduce IO between every function call. But they’re not “managing complexity”, they’re just shifting it into the operational layer, where it’s harder and more expensive to run, debug, secure, etc.

[anonymoushn]

A crypto exchange has bragged about having 30ish microservices per engineer. It's pretty wild.

[jnash]

I think that using the word "stupid" instead of "wild" would be more accurate.

[smrtinsert]

I'd love a number attached to that "most"

[foobiekr]

All but two. And in my previous role that was a very substantial sample set.