Journey to Event-driven Architecture

The world is changing. New problems need to be solved. Companies now run global businesses that span the globe and hop between clouds, breaking down silos to create seamless applications that connect the organisation. There is a continuous state of change that organisations must manage and innovate with. Traditional architectures simply cannot meet the challenges of real time and extreme scale. Today, we are addressing these new, rising needs through microservices, IoT, cloud, machine learning and more. At some point it becomes obvious that we need to go back to basics, back to first principles of system design, and start again. The common element of all these new world problems is that they revolve around the notion of events. These events drive actions and reactions, and transform between different streams, splitting, merging and evolving like the pathways of your brain. To understand the importance of being event driven, we’ll examine why events have become so pivotal in our thinking today. We will then evaluate the qualities and how events have become a first-class concern for the modern organisation, as awareness of events underpins event-first thinking and design. In this discussion we we will examine: History of “events” – Why do they matter? -Adoption journey of the “event” -Considerations of the event-driven architecture -Transitioning to event-first thinking -Event-first versus event-command patterns for event-driven design -Event-command pattern -Benefits of the event-first approach