- 1. Towards a Microservices Architecture
- 2. Five Principles
- Why Principles Matter
- Goals and Principles
- People-First Design
- Rightsized Services
- Build-Services-Only
- Single-Cloud Architecture
- 12 Factor Development
- 1. “One codebase tracked in revision control, many deploys”
- 2. “Explicitly declare and isolate dependencies”
- 3. “Store config in the environment”
- 4. “Treat backing services as attached resources”
- 5. “Strictly separate build and run stages”
- 6. “Execute the app as one or more stateless processes”
- 7. “Export services via port binding”
- 8. “Scale out via the process model”
- 9. “Maximise robustness with fast startup and graceful shutdown”
- 10. “Keep development, staging, and production as similar as possible”
- 11. “Treat logs as event streams”
- 12. “Run admin/management tasks as one-off processes”
- Summary
- 3. Designing Your Microservices Operating Model
- 4. Infrastructure Pipeline
- 5. Building a Microservice Infrastructure
- 6. Designing Microservices: The SEED(S) Process
- Introducing the Seven Essential Evolutions of Design for Services - SEED(S) Method
- Identifying Actors
- Identifying Jobs to Be Done (JTBDs)
- Designing queryable and actionable interaction patterns with Sequence Diagrams
- Deriving actions and queries from JTBDs
- Describing Each Query And Action As A Spec, With An Open Standard
- Getting Feedback on the API spec
- Implementing Microservices
- Microservices vs. APIs
- Summary
- 7. Rightsizing Your Microservices: Finding Service Boundaries
- 8. Dealing with the Data
- 9. Developer Workspace
- 10. Developing Microservices
- 11. Building your Microservice Pipeline: From Test to Release
Microservices: Up and Running
A Step-by-Step Guide to Building a Microservice Architecture
Ronnie Mitra and Irakli Nadareishvili
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.