Monolith to Microservices

Monolith to Microservices by Sam Newman is the definitive field manual for software architects and engineers who need to evolve—not blow up—their existing systems. Rather than advocating a big-bang rewrite, Newman provides a rich catalog of migration patterns (strangler fig, branch by abstraction, tracer write, parallel run, and many more) grounded in real-world case studies from companies like Square, The Guardian, Orbitz, and Homegate. The book begins by establishing what microservices actually are—independently deployable services modeled around business domains—and why independent deployability and information hiding are the load-bearing principles. It then walks readers through whether microservices are even the right choice, how to plan an incremental migration using domain-driven design and organizational change models, how to split both application code and monolithic databases apart safely, and how to anticipate the growing pains—from ownership at scale and breaking changes to distributed tracing and end-to-end testing—that emerge as service counts rise. Newman is unflinchingly honest about the costs and complexity microservices introduce, making this both a how-to guide and a decision-support tool for technology leaders.

What it argues

A causal model describing how architectural design levers and organizational conditions during a monolith-to-microservices migration influence coupling, cohesion, and information hiding, which in turn drive deployment independence, team autonomy, and system-level outcomes including delivery speed, robustness, and operational complexity.