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
Welcome to the first of what is hopefully a regular roundup of what’s new and relevant in the world of microservices. In the past week:
-
Russ Miles (@russmiles) announced µCon, the first conference about microservices. It takes place in London on November 27th-28th.
-
Martin Fowler (@martinfowler) published the final installments of his in-depth article about microservices.
-
Arnon Rotem-Gal-Oz compared microservices with SOA and argued that “microservices” is not a good term.
-
Gawain Hammond (@gawainhammond) wrote a blog post on microservices defending the term “microservices”.
-
@rrees wrote in interesting summary of a session on microservices at the Scale Summit.
-
Chris Richardson (@crichardson) published Thoughts about #microservices – less micro, more service? that suggested that there should be more emphasis on “service” and less on “micro”.
-
There was also the ongoing twitter discussion.
And then there was this:
#microservices pic.twitter.com/T7XOjcUE73
Tom Janssens (@ToJans) March 25, 2014The 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