Book
Building Microservices
Sam Newman
Summary
This second edition has every page reworked from the first, five years after readers reported back what actually broke when their teams adopted microservices. Sam Newman works from the earliest decisions, how to draw a single service boundary and split a monolith, through communication styles, deployment, testing, and monitoring, before turning to security, resiliency, and scaling. New material not in the first edition covers user interfaces, container orchestration, and serverless, folded in alongside real cases from organizations that had already tried these architectures and sometimes failed. It reads less like a tutorial on any one tool and more like an argument for the order in which a team should make these decisions.
Target Readers
- Developers and architects who have decided to build microservices but haven't yet decided how to draw a single service boundary
- Teams mid-migration from a monolith who need a sequence for deciding testing, deployment, and observability, not just a feature checklist
- Engineers who read the first edition years ago and want the added material on container orchestration and serverless
Tags
Colophon
- Publisher
- オライリー・ジャパン
- ISBN
- 978-4814400010
- Published
- Dec 2022
- List price
- ¥4,400incl. 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
Fundamentals of Software Architecture, 2nd Edition
Mark Richards, Neal Ford
Reason: Once you have a vocabulary of architectural characteristics and trade-offs, you apply that judgment to the concrete case of distributed systems. Microservices demand a design that deliberately breaks coupling in exchange for independent deployment and autonomy.
- Recommended
Clean Architecture
Robert C. Martin
Reason: The principles of dependency direction and boundaries apply directly to designing service boundaries. You connect them to concrete decisions that map bounded responsibilities onto independently deployable units.
- Related
Building Micro-Frontends
Luca Mezzalira
Reason: Grasp the idea of splitting the frontend into independent parts, and you notice it shares the same roots as backend microservices. Building Microservices provides the server-side framework of boundaries, autonomous deployment, and alignment with organization, letting you understand the principles of decomposition from both sides.
Next Books
- Recommended
Monolith to Microservices
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.
- Recommended
Designing Data-Intensive Applications
Martin Kleppmann
Reason: Once you split services, the next hard problem becomes the distribution, consistency, and reliability of data. DDIA systematically provides the foundational theory and trade-offs of distributed data systems—replication, partitioning, and transactions.
- Related
Building Applications with AI Agents
Michael Albada
Reason: Learning to design 'autonomous parts that coordinate' with microservices, the idea carries over to multi-agent design that coordinates several AI agents. Practical AI Agent Development becomes an entry point for applying the sense of loose coupling, communication, and responsibility division cultivated in service decomposition to AI systems.