Most people think that event-driven architecture is all about events—services triggering events and asynchronously passing data to other services that respond. But what about the underlying data? How much data should be passed in the event? Where should data be stored and retrieved in a highly loosely coupled system? In this session, you’ll learn about the data side of event-driven architecture—from event contract patterns to various database options, including monolithic data, domain-based data, and service-based data. For each of these database options, you’ll understand the implications, coupling concerns, and trade-offs involved, along with techniques to overcome the challenges of sharing (or not sharing) data. Join this session to discover the "other side" of event-driven architecture.

Target Audience: This session is primarily aimed at Back-end Developers, as they often work with the implementation of event-driven architectures and need to manage data flows between services effectively. Software Architects are the secondary audience, as designing event-driven systems with the correct data strategies is crucial for maintaining scalability and loose coupling. DataTech Professionals will also benefit from understanding how data is handled and stored in event-driven architectures, including the trade-offs between different database strategies.