Microservice Architecture
Supported by KongAbout Microservices.io
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training classes and workshops.
LEARN about microservices
Chris offers numerous resources for learning the microservice architecture.
Training classes
Chris teaches comprehensive workshops and training classes for executives, architectures and developers to help your organization use microservices effectively. Learn how to avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and Kubernetes.
Get the book: Microservice patterns
Read Chris Richardson's book:
Example microservices applications
Want to see an example? Check out Chris Richardson's example applications. See code
BUILD microservices
Consulting services
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
The Eventuate platform
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
ASSESS your architecture
Consulting services
Engage Chris to conduct an architectural assessment.
Self assessment
Alternatively, conduct a self-assessment using the Microservices Assessment Platform.
Join the microservices google group
MicroCPH - Managing data consistency in a microservice architecture using Sagas
In May 2019, I gave a talk at MicroCPH in Copenhagen, Denmark. It focussed on implementing transactions that span services using the Saga pattern.
Abstract
The services in a microservice architecture must be loosely coupled and so cannot share database tables. What’s more, two-phase commit (aka a distributed transaction) is not a viable option for modern applications. Consequently, a microservices application must use the Saga pattern, which maintains data consistency using a series of local transactions.
In this presentation, you will learn how sagas work and how they differ from traditional transactions. We describe how to use sagas to develop business logic in a microservices application. You will learn effective techniques for orchestrating sagas and how to use messaging for reliability. We will describe the design of a saga framework for Java and show a sample application.
Slides
Video
To learn more
- Read my series of blog posts about managing data consistency with sagas
- Look at the complete example code in the eventuate-tram-examples-customers-and-orders Github repository
- Read my Microservices patterns book, which includes a comprehensive discussion of sagas
- Talk to me about my microservices consulting and training services
- Learn more about microservices at learn.microservices.io
The patterns
Application architecture patterns
Decomposition
Deployment patterns
- Multiple service instances per host
- Service instance per host
- Service instance per VM
- Service instance per Container
- Serverless deployment
- Service deployment platform
Cross cutting concerns
Communication style
External API
Transactional messaging
Service discovery
- Client-side discovery
- Server-side discovery
- Service registry
- Self registration
- 3rd party registration
Reliability
Data management
- Database per Service
- Shared database
- Saganew
- API Compositionnew
- CQRS
- Event sourcing
- Application events
Security
Testing
Observability
- Log aggregation
- Application metrics
- Audit logging
- Distributed tracing
- Exception tracking
- Health check API
- Log deployments and changesnew
UI patterns