Book
Monolith to Microservices
Evolutionary Patterns to Transform Your Monolith
Sam Newman
Summary
Sam Newman treats the decision to decompose a monolith as separate from, and often more important than, any specific microservices pattern, and structures the book around evolutionary patterns rather than a single prescribed migration. Central to it is the strangler fig pattern, named for the plant that grows around a host tree and eventually replaces it: new functionality is built as a service while calls to the old implementation are intercepted and redirected, letting a team migrate function by function without a rewrite or a cutover. Later chapters extend the same incremental logic to splitting a database, and the closing chapter is candid about the operational pain decomposition brings even when it's done well.
Target Readers
- Architects planning a monolith decomposition who need a repertoire of incremental patterns, not a single all-or-nothing rewrite plan
- Teams already partway through a migration who are hitting the operational pain of running a hybrid monolith-and-services system
- Engineers who need to split a shared database as part of a service boundary and want patterns beyond the application-layer split
Tags
Colophon
- Publisher
- O'Reilly Japan
- ISBN
- 978-4873119311
- Published
- Dec 2020
- List price
- ¥3,520incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
Clean Architecture
A Craftsman's Guide to Software Structure and Design
Robert C. Martin
Reason: Once you can design boundaries inside a system, you face the next decision: whether to split those boundaries into separate processes—services. Monolith to Microservices, guided by the pragmatic 'monolith first' principle, systematizes the motivations, methods, and pitfalls of decomposition.
- Recommended
Building Microservices
Designing Fine-Grained Systems, 2nd Edition
Sam Newman
Reason: Once you understand microservice principles, you advance to realistic strategies for migrating from an existing monolith. Most successes peel services off a monolith incrementally, so you also learn when not to distribute from the start.
Next Books
- Recommended
Microservices Patterns
With examples in Java
Chris Richardson
Reason: Once you can decide whether to split a monolith, you stock up on the implementation patterns needed after the split. Microservices Patterns catalogs the established practices for service decomposition, data management, communication, and deployment, bridging from 'how to divide' to 'how to build.'
- Recommended
Team Topologies
Organizing Business and Technology Teams for Fast Flow
Matthew Skelton, Manuel Pais
Reason: As you carve out services, the question becomes whether the unit of decomposition matches the cognitive load of a team. The inverse Conway maneuver reorganizes teams to fit the architecture you want.