In an enterprise application, it’s usually a good idea to use a message broker that guarantees at-least once delivery.
At-least once delivery guarantees that a message broker will deliver a message to a consumer even if errors occur.
One side-effect, however, is that the consumer can be invoked repeatedly for the same message.
Consequently, a consumer must be idempotent: the outcome of processing the same message repeatedly must be the same as processing the message once.
If a consumer is not idempotent, multiple invocations can cause bugs.
For example, a consumer of an
AccountDebited message that subtracts the debit amount from the current balance would calculate the incorrect balance.
How does a message consumer handle duplicate messages correctly?
Implement an idempotent consumer, which is a message consumer that can handle duplicate messages correctly. Some consumers are naturally idempotent. Others must track the messages that they have processed in order to detect and discard duplicates.
You can make a consumer idempotent by recording in the database the IDs of the messages that it has processed successfully.
When processing a message, a consumer can detect and discard duplicates by querying the database.
There are a couple of different places to store the message IDs.
One option is for the consumer to use a separate
The other option is for the consumer to store the IDs in the business entities that it creates or updates.
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.
In June, I’ll be teaching a public microservices workshopover Zoom in an APAC-friendly (GMT+9) timezone.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
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 YXEERWTJ to sign up for $195 (valid until May 26th, 2022). There are deeper discounts for buying multiple seats.
Chris offers numerous resources for learning the microservice architecture.
Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help 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.
Delivered in-person and remotely.
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
Application architecture patterns
Refactoring to microservicesnew
Cross cutting concerns