Event Image
Most people think that event-driven architecture is all about events. Services trigger events, asynchronously passing data to other services that respond to those events. 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 the various database options available, including monolithic data, domain-based data, and service-based data. For each of these database options, you’ll learn the implications, coupling concerns, and tradeoffs involved, as well as techniques to overcome some of the challenges of sharing (and not sharing) data. Come to this session to learn the “other side” of event-driven architecture.
Speaker Mark Richards

Mark Richards is an experienced, hands-on software architect involved in the architecture, design, and implementation of microservices architectures and other distributed systems in a variety of technologies. He has been in the software industry since 1983 and has significant experience and expertise in application, integration, and enterprise architecture. Mark is the founder of DeveloperToArchitect.com, a free website devoted to helping developers in the journey to becoming a software architect.

In addition to hands-on consulting and training, Mark has authored numerous technical books, including his three latest books co-authored with Neal Ford: Fundamentals of Software Architecture, Software Architecture: the Hard Parts, and Head-First Software Architecture. Mark has spoken at hundreds of conferences and user groups around the world on a variety of enterprise-related technical topics.

Organizers

AS

Apex Systems
ewoods@apexsystems.com