There has been a shift towards event driven systems since REST and micro-services. Like any other architecture, embarking on an event driven journey, requires plenty of decisions and trade-offs to be made. Prematurely building for the future can lead to under utilization and over-engineering, while focusing solely on the present may result in technical debt and increased costs.

As someone with over 13 years of experience as a software engineering consultant, I've witnessed the challenges and opportunities that businesses face when adopting event-driven architectures. We'll explore the critical aspects to consider, ranging from short-term objectives to long-term vision, the organizational structure's impact, the nature of your business, and the feasibility of your investment.

Join me on this journey, and we'll delve into essential topics such as event modeling, transport mechanisms, governance and different flavors of eventing. I'll also shed light on how these architectural decisions can impact consumers who rely on event streams for critical functions such as analytics and transactional processing.

By the end of this session, you can expect to:
- Gain valuable insights into crafting a well-informed event-driven strategy.
- Understand a mindset shift going event driven and how to choose a platform.
- The discipline to establish when designing events, as they are the building blocks of the future.
- Understand the discoverability, governance and compliance considerations for event-driven systems.

Technical requirements: general software system understanding, distributed systems, event driven architectures

Target audience: CTO's, developers, product people, software philosophy

preferred session duration - 45 mins