the.com/event driven
code that waits for things to happen instead of assuming it knows what's next.
means a system design where actions trigger in response to events—clicks, messages, sensor pings—rather than running in a fixed top-down sequence.
from grew out of gui programming in the 1980s, when interfaces had to react to whichever button a user clicked, not a scripted order of steps; the pattern later scaled up to distributed systems and message queues.
opposite paradigmbatch processing runs on a fixed schedule
core mechanismlisteners wait, dont poll constantly
powerskafka, node.js, and most modern uis
tradeoffflexible, but harder to debug order