Microservices-first approach
The microservices-first approach is an application-development strategy that designs and builds an application as microservices from its inception rather than starting with a monolith.
Microservices Patterns, Second Edition
An application-development strategy that begins by decomposing or building applications as microservices rather than first considering a monolithic design.
- How it is used
- Frames application development around microservices from the outset, rather than beginning with a monolith.
- How deep it goes
- Contrasts adoption strategies and traces deployment, coupling, data, performance, and upgrade consequences, but does not define service boundaries.
- Examples
- Uses FTGO rewrites, acquired applications, new applications, and the main application’s problematic V2 architecture.
- What you can do after
- Evaluate whether microservices solve a tangible problem and choose incremental migration over a risky big-bang or default-first strategy.
Read how Microservices Patterns, Second Edition explains microservices-first approach →
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
An application-development approach in which an application is designed and built as microservices from its inception rather than converted from a monolith.
- How it is used
- Uses greenfield development to establish microservices skills before tackling the harder problem of monolith conversion.
- How deep it goes
- Builds from a minimal application while skimming deep technologies, and stops short of prescribing a perfect or universal implementation.
- Examples
- Demonstrates the approach through a ground-up video-streaming application and a monolith-to-microservices comparison.
- What you can do after
- Build a greenfield microservices application and identify a clearer route from an existing monolith toward microservices.
Related concepts
- microservice architectureuses · Microservice architecture is a software architectural style that structures an application as independently deployable services, typically organized around focused capabilities and communicating through defined interfaces.
- refactoringcontrasts with · Refactoring is the disciplined restructuring of existing software to improve its internal qualities while preserving its externally observable behavior.
Questions about microservices-first approach
What is microservices-first approach?
The microservices-first approach is an application-development strategy that designs and builds an application as microservices from its inception rather than starting with a monolith.
Which Manning books explain microservices-first approach?
Microservices Patterns, Second Edition and Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform.
What is the difference between microservices-first approach and refactoring?
The microservices-first approach is an application-development strategy that designs and builds an application as microservices from its inception rather than starting with a monolith. Refactoring is the disciplined restructuring of existing software to improve its internal qualities while preserving its externally observable behavior.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

