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.
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
I'll be speaking at the YOW! conference and teaching a one day microservices workshop in Sydney and Melbourne. 10% discount with JOINMEATYOW18.
Chris offers a comprehensive set of resources for learning about microservices including articles, an O'Reilly training video, and example code.Learn more
Want to see an example? Check out Chris Richardson's example applications. See code
Join the microservices google group
You have applied the Microservice architecture pattern. The application consists of multiple services and service instances that are running on multiple machines. Errors sometimes occur when handling requests. When an error occurs, a service instance throws an exception, which contains an error message and a stack trace.
How to understand the behavior of an application and troubleshoot problems?
Report all exceptions to a centralized exception tracking service that aggregates and tracks exceptions and notifies developers.
This pattern has the following benefits:
This pattern has the following drawbacks:
Application architecture patterns
Cross cutting concerns