Stop Using Microservices. Build Monoliths Instead

‘Managing Data Is a Nightmare Keeping data in-sync across microservices can be challenging.’ Leaving aside the debate over whether micro services vs monolith is appropriate for your org, this shows me you are thinking about the problem wrong. You shouldn’t have to keep data ‘in sync’ because your domains should be defined in such a way that it doesn’t have to be. In a loosely coupled, event driven system each domain only needs to know information relevant to the business functionality it manages - and in event sourced model even within the domain you have eventual consistency.

In a micro services environment the concept of the ‘global system” state and how the system behaves end-to-end shouldn’t even be something it’s that useful to have to think about and you should start thinking in more local terms about the business functionality you care about.

It's funny how all distilled learnings leap toward instructionalism in the title.

tl;dr loosely coupled microservices have many hard to focus for failure modes that still require a monolithic central understanding by someone.

lite mirror: https://scribe.rip/stop-using-microservices-build-monoliths-...