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 »
What is the event publishing approach called write-aside, and why do you need to be careful when using it. First, what is write-aside?It is when a processor of a request or an event performs its main operation, like updating records in a database, and then afterwards publishes the occurred event to an event platform. Now because the two… Read More »
And will adding the async keyword to my .NET api make it asynchronous? No not in the sense of asynchronous architecture. let me explain. A Restaurant Analogy Let’s take a real-life example of a restaurant. And at this restaurant customers need to go to the counter to get served. In the first example, the server has NOT been… Read More »