Finding OmNomNom's service boundaries
Walking OmNomNom through the questions from the previous post and landing on five boundaries that are nothing like Product, Order, Customer, and Payment.
#distributed-systems
Finding service boundaries is not a naming exercise
Service boundaries are not named into existence. They are discovered by asking who actually gets to decide, what handoffs exist, and where authority quietly leaks.
Service boundaries are about authority
Service boundaries are not about data shape or workflow. They are about authority, and most diagrams skip the part that matters.
Why saga patterns beat orchestration for long-running processes
Orchestration looks great on a whiteboard until your orchestrator becomes the single point of everything
The Two Generals’ Problem and Messaging in Distributed Systems
Two Generals' Problem explained in a Star Wars theme
Distributed Monolith
How can a microservices-based architecture, that looked great on paper, turn into a s...
NDC London 2016 Distributed System Principles
In the eight fallacies, there’s one that says the topology never changes. Isn’t that ...
Distributed Systems Design
Because Blaak Selectie existed for 3 years, Mark and Sandra wanted to organize an eve...