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.
Category: Quarkus
Event-Driven Payment Exceptions Handling Using Kogito
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.
A True Atomic Microservices Implementation with Debezium to Ensure Data Consistency
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.
Migrating a Spring Boot Microservices Application to Quarkus
Let’s walk through a quick tutorial of how to migrate a simple SpringBoot application to Quarkus
So You Want to Build Quarkus Native Image Inside Container, Think Again!
Let us walk through how we failed to build the Jenkins JNPL Slave container for GraalVM with Docker and GraalVM with Podman.