BackendDevOps/CloudHigh signal
Event-Driven Architecture
Also written as EDA
An architecture where services communicate by publishing and reacting to events (things that happened) rather than calling each other directly, letting services stay decoupled from one another.
Think of it like
Like a bulletin board where departments post notices for anyone interested to read, instead of every department having to personally call every other department that might care.
Junior or senior?
Junior sounds like
Describes event-driven architecture only by its decoupling benefits.
Senior sounds like
Can also describe a real debugging challenge it created — tracing a chain of events across services.
Ask them
“What made debugging harder in an event-driven system, compared to services calling each other directly?”