Event‑Driven Architecture is a style where components communicate by publishing and reacting to events. Producers emit events to a broker and consumers handle them asynchronously, decoupling services and improving scalability at the cost of eventual consistency and harder tracing.
Expanding on the short answer — what usually matters in practice:
A tiny example (an explanation template):
// Example: discuss trade-offs for "what-is-event-driven-architecture-(eda)?"
function explain() {
// Start from the core idea:
// An architecture where services communicate by publishing and reacting to events. Producers
}