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.
#microservices
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
Shared database? Of course not!
What is so bad about shared databases with microservices?
Amazon Prime architecture didn’t change
The team at Amazon Prime published an article where they explain their move from serv...
Distributed Monolith
How can a microservices-based architecture, that looked great on paper, turn into a s...
Priority Queues – Interceptors
In the previous articles, I demonstrated why there is not really a need for priority ...
4+1 architectural view model
Once upon a time, I came across a question about a system that was designed according...
Microservices deployment
In the past we used to have monoliths. These were bad. Big balls of mud. Whenever we ...
SDN Presentations on batchjobs and microservices
Today I gave two presentations at an SDN Event in Zeist. An engineer (not the softwar...