Editor's top Microservices books
3Building Microservices (2nd Edition)
Sam Newman · O'Reilly · 284 pages · ~7 hrs to read
The standard text on microservice architecture — decomposition strategies, communication styles, deployment, testing, and organisational implications. The second edition adds a decade of industry lessons about when the pattern hurts.
Microservices Patterns
Chris Richardson · Manning · 898 pages · ~22 hrs to read
The pattern-catalogue companion to Newman — sagas, API composition, CQRS, and the outbox pattern worked through a running example application. Richardson also maintains microservices.io, the free reference site for every pattern.
Release It! (2nd Edition)
Michael T. Nygard · Pragmatic Bookshelf · 490 pages · ~12 hrs to read
The book that named circuit breakers, bulkheads, and the stability patterns every service mesh now implements natively. Written from real production postmortems — this is where "what happens when a downstream service hangs" stops being theoretical.
All Microservices Books
10Building Microservices (2nd Edition)
Sam Newman · O'Reilly · 284 pages · ~7 hrs to read
The standard text on microservice architecture — decomposition strategies, communication styles, deployment, testing, and organisational implications. The second edition adds a decade of industry lessons about when the pattern hurts.
Microservices Patterns
Chris Richardson · Manning · 898 pages · ~22 hrs to read
The pattern-catalogue companion to Newman — sagas, API composition, CQRS, and the outbox pattern worked through a running example application. Richardson also maintains microservices.io, the free reference site for every pattern.
Monolith to Microservices
Sam Newman · O'Reilly · 272 pages · ~7 hrs to read
The migration playbook — strangler fig pattern, database decomposition, and incremental extraction strategies for teams splitting an existing monolith rather than starting greenfield. Grounded in the reality that most microservice work is migration work.
Release It! (2nd Edition)
Michael T. Nygard · Pragmatic Bookshelf · 490 pages · ~12 hrs to read
The book that named circuit breakers, bulkheads, and the stability patterns every service mesh now implements natively. Written from real production postmortems — this is where "what happens when a downstream service hangs" stops being theoretical.
Designing Data-Intensive Applications
Martin Kleppmann · O'Reilly · 662 pages · ~17 hrs to read
Not a microservices book by title, but the distributed systems foundations — replication, partitioning, consistency, consensus — are exactly what makes database-per-service and eventual consistency decisions defensible instead of cargo-culted. Required reading for anyone designing service boundaries around data ownership.
Production-Ready Microservices
Susan J. Fowler · O'Reilly · 172 pages · ~4 hrs to read
Fowler standardized production-readiness across a thousand-plus microservices at Uber, and this book distills that into a concrete checklist — stability, reliability, scalability, monitoring, documentation. Useful as an actual audit tool, not just a reading exercise.
Building Event-Driven Microservices
Adam Bellemare · O'Reilly · 485 pages · ~12 hrs to read
Covers the asynchronous, event-streaming side of microservice communication in depth — event ownership, stream processing topology, and the organizational data-sharing patterns that REST-only architectures never have to solve. Written by a former Shopify staff engineer who built these systems at scale.
Cloud Native Patterns
Cornelia Davis · Manning · 595 pages · ~15 hrs to read
Frames microservices as one piece of a broader "change-tolerant software" mental model alongside containers, orchestration, and config management. A good bridge between the architecture-pattern books and the platform-engineering tooling that runs microservices in production.
Microservices for the Enterprise
Kasun Indrasiri & Prabath Siriwardena · Apress · 434 pages · ~11 hrs to read
Addresses the unglamorous reality most microservices work actually involves: brownfield adoption alongside legacy systems and ESBs, not greenfield builds. The API management and service integration chapters are useful for engineers at large, non-Netflix-shaped organizations.
Domain-Driven Design
Eric Evans · Addison-Wesley · 563 pages · ~14 hrs to read
The origin of "bounded context," the concept every microservice decomposition strategy is built on whether or not the team knows it. Dense and dated in places, but the core ideas about modeling around business domains rather than technical layers are exactly what separates a well-decomposed service boundary from an arbitrary one.
Microservices resources
Learn next