Course of Event Bus in a Database [Infrastructure Design]

💸 First lesson available without registration 💸

There comes a time when our applications need to scale in terms of functionality.

When a user registers, we need to send them an email, generate some suggestions for them… and to make the code easier to modify and test, we introduce an in-memory Event Bus.

Then there comes a point where we cannot afford for everything to execute sequentially, we need asynchronicity for those derived cases.

At that moment, the most common thought is to consider adding a messaging system like RabbitMQ, AWS Event Bridge, or Kafka, but that requires adding a new piece of infrastructure.

In this course, we explore another way: Using our own database for it.

In this way, the friction is minimal. For this, we explore:

• 💣 Different alternatives on how to publish and consume messages
• 💻 How to generate all the parts we can automatically
• 🔥 How to manage errors with retries and dead letters

All of this questioning why we use the architecture we use and seeing its alternatives.