✳flâneur — a map of the web's best reading

Implementing the Transactional Outbox Pattern with Debezium in Quarkus | by Iain Porter | Level Up Coding

levelup.gitconnected.com · 1,338 words · saved by 1 readers

T his is the second instalment in a series on building a microservice from the ground up with Quarkus, Kotlin and Debezium. In part one we built a simple REST API in Quarkus for persisting SMS messages. We used testcontainers to run the service in a docker container and establish that everything worked as expected. In this part we’ll use the transactional outbox pattern to generate events when the messages are persisted. We can then process the messages asynchronously and, ultimately, get the SMS message to the end user’s mobile device. A common pattern in microservices is to generate events when an entity has changed. This allows consumers to be notified of any changes. However we are dealing with two separate transactions: write to the database and publish to a message broker. To avoid the complexity that comes with XA transactions we can achieve an atomic transaction by writing the event to an Outbox table as part of the same transaction that persists the entity change. Both persist

Implementing the Transactional Outbox Pattern with Debezium in Quarkus Iain Porter 6 min read · Jul 29, 2020 -- Listen Share Press enter or click to view image in full size Photo by Matthew Henry from StockSnap T his is the second instalment in a series on building a microservice from the ground up with Quarkus, Kotlin and Debezium. In part one we built a simple REST API in Quarkus for persisting SMS messages. We used testcontainers to run the service in a docker container and establish that everything worked as expected. In this part we’ll use the transactional outbox pattern to generate even

Explore this link on the map →

related reading