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 Microservices architecture pattern and the Database per service pattern. As a result, it is no longer straightforward to implement queries that join data from multiple services. Also, if you have applied the Event sourcing pattern then the data is no longer easily queried.
How to implement a query that retrieves data from multiple services in a microservice architecture?
Define a view database, which is a read-only replica that is designed to support that query. The application keeps the replica up to data by subscribing to Domain events published by the service that own the data.
My book’s FTGO example application has the
Order History Service, which implements this pattern.
There are several Eventuate-based example applications that illustrate how to use this pattern.
This pattern has the following benefits:
This pattern has the following drawbacks:
Application architecture patterns
Cross cutting concerns