Event-driven programming
programming paradigm
In computer programming, event-driven programming is a programming paradigm in which the flow of the program is determined by external events. User interface (UI) events from keyboards and mice, touchpads and touchscreens, and external sensor inputs are common cases. Events may also be programmatically generated, such as from messages from other programs, notifications from other threads, or other network events.
Event-driven programming is the dominant paradigm used in graphical user interface (GUI) applications and network servers.
In an event-driven application, there is generally an event loop that listens for events and then triggers a callback function when one of those events is detected.
Event-driven programs can be written in any programming language, although the task is easier in languages that provide high-level abstractions.
Although they do not exactly fit the event-driven model, interrupt handling and exception handling have many similarities.
It is important to differentiate between event-driven and message-driven (aka queue-driven) paradigms: event-driven services (e.g. AWS SNS) are decoupled from their consumers, whereas message/queue-driven services (e.g. AWS SQS) are coupled with their consumers.
“Event-driven programming” enters the record as programming paradigm. Crown Archives preserves that source wording while asking what Event-driven, programming and paradigm can confirm, complicate or overturn.
Why this record matters
“Event-driven programming” is worth following because a concise public description often conceals a longer documentary argument. Here, Event-driven, programming and paradigm provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Aug 29, 2026. The linked authority identifier is Q1135914. None of the 0 selected statements returned an explicit reference.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Event-driven programming”, its source revision and the description used here.
- Expand the search: follow Event-driven programming primary sources, Event-driven programming archive and Event-driven research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Event-driven programming”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Event-driven programming” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.