3 ms·

I think microservices are supposed to be easier to deploy independently, that's the whole point. And if they are not, it means you're just doing it wrong. But

I think microservices are supposed to be easier to deploy independently, that's the whole point. And if they are not, it means you're just doing it wrong. But in truth, all the projects with microservices I have seen in real life had deployment coordination problems, and looked to me like distributed monoliths. So maybe it's a 'no true scotsman' thing. Maybe they are always, or at least most of the time, harder. Makes it harder to justify using them.

xboxnolifes 1mo ago
People do microservices (read: an API spread across multiple processes), but then make all of the mistakes that logically couple the service deployments together. They use shared databases instead of one per service, make breaking changes to API schema instead of non-breaking or versioning, use a shared library of schema definitions instead of having each service define their own data objects for API calls, and have startup logic that depends on another service being up.