Building Microservices
by Sam Newman · Sam Newman
Sam Newman covers how to decompose a system into services and then run them: modeling boundaries, integration styles, versioning, deployment, testing, monitoring, security. Readers finish able to reason about where service boundaries belong and what operational cost they carry.
This link may earn us a small commission at no extra cost to you. Affiliate disclosure
More resources on Microservices
microservices.io
Microservices.io is a detailed resource on microservices architecture, offering patterns, principles, and practical guidance for building and operating microservice-based systems. It covers decomposition strategies, inter-service communication, data management, testing, deployment, and governance patterns to apply proven approaches.
Martin Fowler's Microservices Guide
James Lewis and Martin Fowler's 2014 essay defining the microservice architectural style: componentization via services, decentralized data, smart endpoints, infrastructure automation. Readers come away able to name the nine characteristics and weigh the trade-offs against a monolith.
Microservices Patterns
Chris Richardson catalogues 44 patterns for service decomposition, inter-service communication, sagas for distributed transactions, CQRS querying, and testing. Worked Java examples let readers pick a pattern for a given consistency or coupling problem rather than guessing.
Monolith to Microservices
Sam Newman treats decomposition as an incremental migration: strangler fig, branch by abstraction, parallel run, and the harder job of splitting a shared database. Readers finish able to sequence a migration and to judge when not to start one.