When you consider Domain-Driven Design when building systems and applications, you might be wondering why should you even consider using Event Sourcing? Is it because the original name of Event Sourcing was "Distributed DDD", and "DDD/ES/CQRS" became somewhat a classic set of acronyms? In fact, when you read an event sourcing-oriented article from a vendor like Confluent or Amazon AWS, you find little connection between what they mean by "Event Sourcing" and Domain-Driven Design.

It looks like the connection between DDD and Event Sourcing is getting lost at times. However, I still believe that Event Sourcing has lots of benefits when being used to build a system following the DDD principles. I will share some of the key points that make this synergy obvious and appealing during this talk. I'll also tell some stories from the field when developers gained so much from parts of the systems they built being event-sourced that they can hardly imagine doing anything else.