4 ms·
Good point and I do agree to an extent. However, without discipline we are simply moving the risk. Eg. We can't enforce interface boundaries in our system vs. w
by josho 11y ago
Good point and I do agree to an extent. However, without discipline we are simply moving the risk. Eg. We can't enforce interface boundaries in our system vs. we have a micro service architecture with N systems that we need to deploy as a monolith because we don't have the discipline to ensure backwards compatibility between systems.
Yes. My current enterprise client takes a week to deploy their micro service arch. Because all systems need to be deployed at once.
So, they simply traded one complexity for another without fixing the root problem--a disciplined development methodology.
- beat 11y agoYeah, I think there's a problem with the definition of microservices in theory vs in practice. In theory, the boundary of a microservice is the api, right? In practice, the boundary is the set of things you must change in order to update one part. If you have to DEPLOY ALL THE THINGS!!!! in order to update a single component, it's not a microservices architecture. Not in practice, anyway. It's a monolith with a bunch of different moving parts.