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.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.
Get the book: Microservices 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
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
Data management
Transactional messaging
Testing
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
Service discovery
- Client-side discovery
- Server-side discovery
- Service registry
- Self registration
- 3rd party registration
Reliability
Security
Observability
- Log aggregation
- Application metrics
- Audit logging
- Distributed tracing
- Exception tracking
- Health check API
- Log deployments and changesnew
UI patterns