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.
Chris offers numerous resources for learning the microservice architecture.
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.
Want to see an example? Check out Chris Richardson's example applications. See code
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
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.
Join the microservices google group
The Microservice Architecture Assessment is a distillation of my experiences training and consulting at organizations around the world. It’s for organizations that are currently developing a microservices-based application. The Microservice Architecture Assessment evaluates what you have built and tells you how to improve it. By using the Microservice Architecture Assessment, you reduce architectural and organizational risk and maximize the benefits of the microservice architecture.
The assessment consists of two types of questionnaires. The first assesses multiple aspects of your application architecture, organization and process. The second type of questionnaire is used to assess an individual service. By evaluating an application and each of its services, the Microservice Architecture Assessment evaluates your current architecture, identifies weaknesses and suggests improvements.
Application architecture patterns
Cross cutting concerns