Consider, the FTGO application, which is an online food delivery application.
A client of application creates an order by making an HTTP POST /orders
request and expects a response, say, within 600ms.
Because the FTGO application uses the microservice architecture, the responsibilities that implement order creation are scattered across multiple services.
The POST
request is first routed to the Order Service
, which must then collaborate with the following services:
Restaurant Service
- knows the restaurant’s menu and pricesConsumer Service
- knows the state of the Consumer
that places the orderKitchen Service
- creates a Ticket
, which tells the chef what to cookAccounting Service
- authorizes the consumer’s credit cardThe Order Service
could invoke each of these services using synchronous request/response.
It might, for example, implement the inter-service communication using REST or gRPC.
However, a key drawback of using synchronous request/response is that it reduces availability.
That’s because if any of the Order Sevice
’s collaborators are unavailable, it will not be able to create the order and must return an error to the client.
An alternative approach is to eliminate all synchronous communication between the Order Service
and its collaborators by using the CQRS and Saga patterns.
The Order Service
can use the CQRS pattern to maintain a replica of the restaurant menu’s and there by eliminate the need to synchronously fetch data from the Restaurant Service
.
It can validate the order asynchronously by using the Saga pattern.
The Order Service
creates an Order
in a PENDING
state and sends back a response to the POST /order
.
It then completes the creation of the order by communicating asynchronously with the other services.
A key benefit of this approach is that it improves availability.
The Order Service
always respond to a POST /orders
request even when one of the other services is unavailable.
One drawback, however, of using a saga to complete the creation of the order is that the response to the POST
doesn’t tell the client whether the order was approved.
The client must find out by periodically invoking GET /orders/{orderId}
.
How should a service collaborate with other services when handling a synchronous request?
Design a service so that it can respond to a synchronous request without waiting for the response from any other service.
One way to make a service self-contained is to implement needed functionality as a service module rather than a separate service.
We could, for example, merge the Order Service
and Restaurant Service
.
Another way to make a service self-contained is for it to collaborate with other services using the CQRS and the Saga patterns. A self-contained service uses the Saga pattern to asynchronously maintain data consistency. It uses the CQRS pattern to maintain a replica of data owned by other services.
The Order Service
in the FTGO application described earlier is an example of a self-contained service.
The createOrder()
operation, for example, queries a CQRS replica of data owned by the Restaurant Service
to validate and price the order, and then initiates a saga to finish the creation of the order.
This pattern has the following benefits:
This pattern has the following drawbacks:
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 workshops.
Chris teaches comprehensive workshops for architects and developers that will enable 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.
Learn moreChris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon RESVJCMC to sign up for $95 (valid until September 26th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
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.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
Microservices adoption · ancient lore · anti-patterns · application api · application architecture · architecting · architecture · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · developer experience · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · modular monolith · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service architecture · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging
Application architecture patterns
Decomposition
Refactoring to microservicesnew
Data management
Transactional messaging
Testing
Deployment patterns
Cross cutting concerns
Communication style
External API
Service discovery
Reliability
Security
Observability
UI patterns