Async Glossary
Browse 35 async terms defined in plain English, from the cultural dictionary of computing.
35 Async Terms
- Async Error
- An error that occurs in asynchronous execution, often outside the original call site that scheduled the work. Async errors are harder to debug than synchronous...
- Async Function
- A function that can suspend while waiting for asynchronous operations and resume later, usually returning a promise, future, or similar awaitable result. Async...
- Async Hook
- A callback or instrumentation mechanism that runs when asynchronous resources are created, executed, or completed. Async hooks are commonly used for tracing,...
- Async Lock
- A synchronization primitive used in asynchronous code to ensure only one task or a limited set of tasks can enter a critical section at a time without blocking...
- Async Pattern
- A recurring way of structuring asynchronous work, such as fan-out/fan-in, pipelines, task queues, backpressure, or cancellation-aware execution. Choosing the...
- Async Pool
- A mechanism for limiting and coordinating how many asynchronous tasks may run concurrently, often to avoid overwhelming external services or local resources....
- Async Queue
- A queue used to hand off units of work for asynchronous processing so producers and consumers do not need to run in lockstep. Async queues help smooth spikes,...
- Async Stream
- A sequence of values or chunks produced and consumed asynchronously over time rather than all at once. Async streams are used for large data processing,...
- Async Task
- A unit of work scheduled to run asynchronously rather than immediately inline with the caller. Async tasks are common in job systems, event loops, UI...
- Background Queue
- A queue used to hold work that should be processed later by background workers rather than during the original request or interaction. Background queues help...
- Background Task
- A unit of work scheduled to run outside the immediate foreground flow, often after the user has already received a response. Background tasks are useful for...
- Callback
- A function passed to another function or system to be invoked later in response to an event, completion, or decision point. Callbacks are a foundational...
- Callback Function
- A function intended to be called by another piece of code after a task completes or an event occurs, often with data about the outcome. The phrase emphasizes...
- Callback Hell
- Callback Hell, also known as the pyramid of doom, is a code antipattern in asynchronous programming where multiple nested callback functions create deeply...
- Command Queue
- A queue that stores commands for later processing by one or more workers or handlers. Command queues are useful when commands should be decoupled from the...
- Coroutine
- A generalization of subroutines that can suspend execution at certain points and resume later, enabling cooperative multitasking without threads. Used...
- Event-Driven Architecture
- A design paradigm where the flow of the program is determined by events — user actions, sensor outputs, messages from other services. Components publish events...
- Event Loop
- Event Loop is a programming construct that continuously monitors for and dispatches events or messages in a program, enabling asynchronous, non-blocking I/O...
- Future
- A placeholder for a value that will be available at some point in the future, representing the result of an asynchronous computation. Called Future in...
- Message Queue
- A message queue is a middleware system enabling asynchronous communication between services. Producers send messages to a queue, where they are stored until...
- Promise
- Promise is an object in asynchronous programming that represents the eventual completion (or failure) of an asynchronous operation and its resulting value. A...
- Promise.all
- A JavaScript method that takes an iterable of Promises and returns a single Promise that resolves with an array of all results when every input Promise...
- Promise Chain
- A sequence of .then() calls on a JavaScript Promise where each callback receives the resolved value of the previous step and returns a new value or Promise,...
- Queue
- A first-in, first-out (FIFO) data structure where elements are added at the back and removed from the front. In distributed systems, message queues (RabbitMQ,...
- Reactive Programming
- A programming paradigm oriented around asynchronous data streams and the propagation of change, where the runtime automatically updates dependent computations...
- Reactive Stream
- A specification (originally the Reactive Streams initiative for JVM languages) for asynchronous stream processing with non-blocking backpressure, defining...
- Redux Thunk
- A Redux middleware that allows action creators to return functions (thunks) instead of plain action objects, giving them access to dispatch and getState so...
- Stream
- A sequence of data elements made available over time, processed incrementally rather than loaded entirely into memory, used for file I/O, network...
- Suspension Point
- A location in a coroutine or async function where execution may be paused and the thread yielded back to the scheduler until a result is available. In Kotlin,...
- Task
- A unit of work that can be scheduled and executed, often asynchronously. In modern runtimes, tasks are lighter than threads and managed by an executor or event...
- Task Queue
- A data structure or service (like Celery, Sidekiq, or Bull) that holds units of deferred work in a FIFO or priority queue, allowing producer processes to...
- Timer
- A programming construct that triggers a callback or event after a specified delay (one-shot) or at recurring intervals — implemented via functions like...
- Top-Level Await
- A JavaScript feature (ES2022) that allows the `await` keyword to be used at the module's top scope rather than only inside async functions, causing the module...
- Waker
- In Rust's async runtime model, a handle provided to a Future when it is polled that the future stores and later uses to signal the executor that it is ready to...
- Warp
- A lightweight, composable web framework for Rust built on top of hyper, where routes and middleware are modeled as combinable Filters that can be chained with...
Related Topics
- Concurrency (11 terms in common)
- Javascript (6 terms in common)
- Queues (3 terms in common)
- Functions (3 terms in common)
- Kotlin (2 terms in common)
- Background Jobs (2 terms in common)
- Rust (2 terms in common)
- Architecture (2 terms in common)
- Scheduling (2 terms in common)
- Tasks (2 terms in common)
- Java (1 terms in common)
- Streams (1 terms in common)
- I/O (1 terms in common)
- Background Work (1 terms in common)
- Events (1 terms in common)
- Work Distribution (1 terms in common)
- Debugging (1 terms in common)
- Instrumentation (1 terms in common)
- Synchronization (1 terms in common)
- Patterns (1 terms in common)