Event Driven
Last updated
What is Event Driven?
Event-driven architecture (EDA) is a software design pattern in which the system reacts to specific events that occur, rather than being continuously polled for changes. In EDA, events are messages that are sent asynchronously between components, and the components react to the events they are interested in.
The main advantage of using EDA is that it allows for a clear separation of concerns between the components, and it can improve the scalability and fault-tolerance of the system. Additionally, it allows for loose coupling between components, meaning that the components are not aware of each other's existence, and can be developed, deployed, and scaled independently.
Free resources to learn Event Driven
More in stage 7: Messaging
- Messaging
- GoF Design Patterns
- PoSA Patterns
- Composition over Inheritance
- Encapsulate what varies
- Program against abstractions
- Domain Models
- Anemic Models
- Domain Language
- Class Variants
- Layered Architectures
- Client-Server
- Publish-Subscribe
- Peer-to-Peer
- Component Principles
- Policy vs Detail
- Coupling and Cohesion
- Boundaries
Event Driven: common questions
Can I learn Event Driven in Hindi?
This lesson is written in English. Once you sign in, open it in the interactive course and ask the AI tutor to explain Event Driven in Hindi or Hinglish. The tutor answers from this lesson’s own text, so it stays on the syllabus, and it runs on your own Google, OpenAI or Anthropic key.
Is this Event Driven tutorial for beginners?
It is lesson 57 of 94 in the free Software Design and Architecture roadmap, in stage 7, Messaging. If you are new to Software Design and Architecture, start from stage 1 and come back here in order; if you already know the earlier stages, this lesson stands on its own.