OmNomNom
A walk through OmNomNom, a demo built to make service boundaries visible in code. Starts with what a service boundary actually is and works out from there.
-
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.
-
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.
-
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.
-
One product page, three services
Catalog owns the name, Finance owns the price, and Marketing owns the rating. How does OmNomNom turn those separate contributions into one product page?
-
Composing product lists with ServiceComposer
A product identifier lets services work independently. A product list first needs someone to select the products. How composition events provide that context without a central controller knowing every service.
