Synthesis work is where boundary theory becomes reusable architecture judgment. Chapter 16 closes the guide with two reference architectures, two case studies, and one decision framework that pulls together capability fit, data ownership, workflow coupling, team structure, and operational cost.
Read the lessons in order. The first two show plausible steady-state reference shapes for a small product team and a growing SaaS platform. The next two use e-commerce and an internal enterprise platform as realistic decomposition case studies. The final lesson turns the whole guide into a reusable boundary-review framework.
If a team needs more than principles and wants concrete examples to compare against its own system, this chapter is the practical bridge.
In this section
- Reference Architecture for a Small Product Team
A practical lesson on a modest reference architecture for a small product team, showing when a modular monolith or a very small number of services is the healthier boundary choice.
- Reference Architecture for a Growing SaaS Platform
A practical lesson on a more mature SaaS reference architecture with capability-oriented services, selective event-driven integration, clear data ownership, and stronger platform support.
- Case Study on Decomposing an E-Commerce Platform
A practical case study showing how an e-commerce platform can evolve from an overloaded monolith toward stronger boundaries around catalog, checkout, billing, inventory, and fulfillment.
- Case Study on Splitting a Legacy Internal Platform
A practical case study on decomposing a legacy internal enterprise platform under political, compliance, and shared-database constraints.
- A Decision Framework for Drawing Better Boundaries
A practical lesson that turns the guide into a reusable decision framework for reviewing candidate service boundaries across capability fit, data ownership, workflow coupling, team ownership, and operational cost.