The answer is yes. You can combine the two. Let’s look at two possible solutions. FYI, I am basing the solution on a question I received on one of my videos https://youtu.be/U-U3bpljZd0. The question was: Possible Solution Key architecture design decisions for my approach Before we go through the two approaches, let me share my architectural design decisions.… Read More »
An example of the additional complexities which event-driven architecture brings. In this example, I use a combination of Apache Kafka (AWS MKS), Oracle, and Amazon Data Migration Service (AWA DMS) to change an existing synchronous request-driven microservice to a asynchronous event-driven solution.
Have you watched the video How to handle message retries & failures in event driven-systems? Handling retires with Kafka? , but you need more information. Hopefully this post helps. Let’s say you have a consumer, a retry consumer, subscribing to a retry topic. When the retry consumer consumes the retry topic and retrieves message/s, the consumer must check… Read More »
Why do I insist on designing APIs first before any code is written. Read my journey
In the post, How to handle retry messages and failures when using event streaming platforms like Apache Kafka, I walked through how to retry events when using Apache Kafka. Now in this post, I will discuss an approach you can implement to ensure processors process events in order even when you’ve implemented a retry solution. YouTube video After… Read More »
What is the outbox pattern? It is when a request or the event processor performs its database transaction operation but does not publish the occurred event afterwards. Instead, during the database transaction, a record or multiple records are inserted into a dedicated database table, the outbox table, which holds the records which you want to publish to a… Read More »