Software → Programming
Event-Driven Programming
A style where program flow is driven by events such as user actions, messages, or signals.
Motivation
Event-Driven Programming exists because teams need a practical way to solve a recurring problem in real systems. It gives engineers a shared abstraction for discussing trade-offs instead of treating every implementation as unique.
Where it fits
Event-Driven Programming belongs to the software track in the programming layer. It is useful when reasoning about nearby concepts such as Event-Driven Architecture, Publish-Subscribe.
Mental model
Think of Event-Driven Programming as a named design pressure: it usually improves one quality, such as scalability, safety, usability, or operability, while adding constraints that must be understood.
Example in practice
When Event-Driven Programming appears in a system, the important question is not only what it is, but why the system needs it and what failure modes it introduces.
Common mistakes
- Using Event-Driven Programming because it is fashionable rather than because the problem requires it.
- Ignoring the operational cost or learning curve.
- Treating the concept as isolated instead of connecting it to neighboring concepts.