In my previous post, I briefly talked about event-based architecture for payment platform modernization and why the modernization is important to the industry. In this post, we will dive into details of the key capabilities to consider for the payment platform modernization. The capabilities covered in this post may not be the complete list but it definitely serves as a good start.
Category: Event-Driven Payment
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.
Payment Platform Modernization With Event-Based Architecture
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
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.