> 23 microservices he had carved up out of a Java Spring app. A small change anywhere in the code meant he had to redeploy all of it,
Those aren't microservices, by definition.
Those aren't microservices, by definition.
Pretty sure that's the point OP was trying to make - they put in the effort to build microservices, and crappy tooling means they are instead stuck with an mangled over-engineered monolith
Regardless, it doesn't sound like microservices, it sounds like a distributed monolith.
Having built a product out of microservices and lambdas I definitely have not found that build tooling has ever forced a full redeploy. I suspect this is just a case of converting a monolith to a microservice being much more difficult than people realize.
Yea, you are probably right on the money.
IME lots of folks struggle with DRY when trying to actually implement their services. In teams I work with, we frequently see attempts to build a shared library and have to re-hash the discussion every time
If your application does not meet any of those requirements then call it something else, as it clearly isn't a microservice.
Not sure you read my post. I called it a "mangled over-engineered monolith"