Unless you're working on an isolated monolith, you probably need to inform other parts of your system that things happened in your application or service. This is often done using the transactional outbox pattern where events are stored in your relational database and another process publishes those events on a message broker.

As with everything we do, every choice has its pros and cons, and this traditional implementation also has its limitations. In this talk we'll explore other shades of the outbox pattern, without diving into event sourcing. That’s a different architectural paradigm altogether. We'll discover different ways of tracking events, how to publish them and different ways of consuming those events that suit the needs of the consumers.

It always depends. Leave this talk armed with new alternatives in creating reliable systems and the know-how to implement them.