Event-driven programming is a programming paradigm where the flow of the program is determined by events such as user actions, sensor outputs, or messages from other programs or threads. In event-driven programming, there is generally a main loop that listens for events and then triggers a callback function when one of those events is detected.

How to use it in a sentence

• I tried to debug Dave's event-driven programming monstrosity last night but gave up after my fifth Red Bull and 20th existential crisis.

• My PM keeps raving about serverless and event-driven programming - I'm pretty sure he just learned those buzzwords at some blockchain conference and has no idea what they actually mean.

If you actually want to learn more...

Here are a few articles that might be helpful if you really want to dive into the exhilarating world of event-driven programming:

• What do you mean by "Event-Driven"? - Martin Fowler breaks down different flavors of event-driven architectures, if you're into that sort of thing.

• The LMAX Architecture - An overview of the LMAX retail trading architecture which can process 6 million orders per second on a single thread. It's like the Chuck Norris of event processing.

• Focusing on Events - More ponderings from Martin Fowler on event-driven approaches, in case the first article wasn't enough to satiate your curiosity.

Note: the Developer Dictionary is in Beta. Please direct feedback to skye@statsig.com.