Building Microservices, 2nd Edition (Early Release, Raw and Unedited)

Building Microservices (2nd Edition) distills years of real-world experience into a comprehensive, opinionated guide to service-oriented architectures done well. Sam Newman shows how to draw stable service boundaries around business domains using information hiding, coupling, and cohesion; how to choose communication styles (synchronous vs asynchronous, request-response vs event-driven) and matching technologies (REST, gRPC, GraphQL, message brokers); how to coordinate multi-service workflows with sagas rather than distributed transactions; and how to build, deploy, and progressively release microservices using CI/CD, containers, Kubernetes, and FaaS. Rather than treating microservices as a fashionable default, the book frames them as an architectural choice that 'buys you options' at a cost—flexibility in technology, scaling, robustness, and organizational alignment, offset by the complexity of distributed systems. It's essential reading for architects and developers who want the benefits of independent deployability without falling into the trap of a distributed monolith.

What it argues

A causal model linking architectural and organizational design levers (boundary design, information hiding, isolation, automation) through psychological/behavioral and structural states (coupling, cohesion, temporal coupling, developer productivity) to outcomes such as independent deployability, robustness, scalability, and delivery speed.

Key ideas it contributes

• Information Hiding — The deliberate concealment of a service's internal implementation behind its interface, exposing only what is necessary.
• Domain-Oriented Boundary Design — The degree to which service boundaries follow business domains (bounded contexts/aggregates) rather than technical layers.
• Coupling Between Services — The extent to which a change in one service necessitates a change in another.
• Cohesion Within Services — The degree to which related behavior is grouped within a single service so it can be changed in one place.
• Temporal Coupling — A runtime dependency requiring collaborating services to be simultaneously available for an operation to succeed.
• Explicit Interface Schema — A formal, versioned definition of a service's accepted inputs and exposed outputs.
• Backward Compatibility Discipline — The consistent practice of evolving interfaces without breaking existing consumers.
• Isolated Execution Environment — The provision of a ring-fenced runtime with dedicated resources for each service instance.