IDG Contributor Network: Busting event-driven myths
If you think an event-driven architecture isn’t for you, think again: you might be missing out on useful design patterns that will future-proof your applications.
In the past few years, there has been an increase in popularity of event-driven architectures: more conference talks, blog posts, Slack discussions, and tweets on the subject. While event-driven architectures are not a new concept, they are especially well suited to recent trends in software engineering, including cloud computing, microservices, and scaling by building flexible, distributed systems, which explains why they are becoming more popular.
Event-driven architecture is the idea that one should design software starting with events, things that happen in the real-world and have real business meaning, and that these events should be the central concept in the architecture. Data is front-and-center, and components create events, handle events and send events to each other. There are several software design patterns that are particularly suited for event-driven architectures, such as event notification, event-carried state, and event sourcing.