17 years helping Israeli businesses
choose better software
Event-driven Architecture (EDA)
Event-driven architecture (EDA) is a software design approach in which a software component executes in response to receiving one or more event notifications. Events, or a change caused by a user's action, trigger the services, or operations, of the software. One example of an event is a new user clicking the sign-up button that creates an account. EDA components include events, a service/event handler, event loops, and event flow layers.
What Small and Midsize Businesses Need to Know About Event-driven Architecture (EDA)
EDA is useful in designing systems: to monitor and receive alerts to anomalies or changes; to push out a single event to multiple consumers; to provide interoperability between different technologies; and, to coordinate systems and teams across different regions and accounts. SMBs can incorporate EDA to achieve both flexibility and scalability, for real-time adaptation and decision-making.
Related terms
- Haptics
- WAN (Wide-Area Network)
- Intranet
- SLO (Service-Level Objective)
- Security Orchestration, Automation and Response (SOAR)
- Scalability
- Service-Level Agreement (SLA)
- Software as a Service (SaaS)
- Identity and Access Management (IAM)
- Data Center
- Augmented Reality (AR)
- Synchronous
- Multitenancy
- Chief Information Officer (CIO)
- IT Services
- Authorization
- Service-oriented Architecture (SOA)
- Platform as a Service (PaaS)
- Managed Service Provider (MSP)
- Security Information and Event Management (SIEM)