Debezium is developed base on Kafka Connect framework and we need Apache Kafka cluster to store the captured events data from source databases. Sometime we do not require the level of tolerance and reliability provided by Apache Kafka cluster, but you still need Change Data Capture (CDC). This is where Debezium Engine come into the picture.
Let’s go through in detail how can we use the Kogito services to help us to modernise the payment platform by following the event-driven architecture approach. Kogito is the right fit in the scenarios where you need to implement decision services and business automation for an event driven architecture, with the fact that it is purposely built for events and cloud-native use cases.
When the CODIV-19 pandemic started nearly 2 years ago, many were not prepared and suffered a great pain to maintain normal life, including the businesses… This is no different for the payment industry … the payment industry is one the most needing rapid innovation and change to stay ahead of competitions … the industry players need a new approach for their payment platform… Payment platform modernization is a journey and this journey will be less painful when you have done it right at the beginning
Typical microservices outbox pattern implementation requires developers to manually create the outbox event table and write the codes to send the data from the outbox table to the respective messaging platform. Debezium Outbox Event Router together with Outbox Quarkus Extension take cares of this and enforce a standard approach to do this with declarative implementation. This allows the developers to focus on business logic implementation and achieve faster application delivery.
Let’s walk through a quick tutorial of how to migrate a simple SpringBoot application to Quarkus