Microservice Architecture
Supported by KongAbout Microservices.io
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action and the creator of the original CloudFoundry.com. His latest startup is eventuate.io, a microservices application platform.
Microservices consulting and training
Chris offers a comprehensive consulting services, workshops and hands on training classes to help you use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and Kubernetes. Find out more
Public workshops in Chicago and Stockholm
In May, I am teaching a couple of public workshops in Chicago and Stockholm, Sweden
Learn more about microservices
Chris offers a comprehensive set of resources for learning about microservices including articles, an O'Reilly training video, and example code.
Learn moreExample microservices applications
Want to see an example? Check out Chris Richardson's example applications. See code
Get the book: Microservice patterns
Join the microservices google group
CodeFreeze 2018 - There is no such thing as a microservice!
In early January, I gave a keynote at Code Freeze 2018 in Minneapolis. This fantastic conference lived up to its name - with windchill it was -9F outside. Here I am with the other keynote speakers: @randyshoup and @micheletitolo
About the keynote
The title of the talk was “There is no such thing as a microservice!”. The key points are:
- The microservice architecture is an architectural style that structures an application as a collection of loosely coupled services.
- The goal is to support the continuous delivery/deployment of software by small, autonomous teams. Each team is responsible for one or more services. Service size is much less important.
- It makes little or no sense to discuss individual microservices or, for example, to “use a microservice to solve a problem”.
- The microservices pattern language enables you to solve key problems when using the microservice architecture
- An event-driven architecture is a good way to tackle distributed data management challenges that arise microservice architecture.
Slides
Here are the slides:
Video
Here is the video:
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