scheduler
A component that decides which piece of pending work runs next and when, based on priorities.
In more detail
Operating systems, container orchestrators, job queues and user interface libraries all have schedulers, each deciding what runs next in its own domain. A good scheduler keeps urgent work fast while still finishing everything eventually.
Example
React has its own scheduler package that runs rendering work in short slices and orders it by priority lanes.Related terms
- orchestration — Automatically deploying, scaling, restarting and moving containers across a group of machines.
- rolling update — Replacing instances of an application with the new version a few at a time while the rest keep serving.
- eviction — Removing a running pod from its node, either through the API during maintenance or by the kubelet when the node runs short of resources.
- time slicing — Splitting a long job into short slices and giving control back to the browser between them so the page stays responsive.
- lane — The internal React label for the priority of an update, stored as one bit in a number so many priorities can be combined and compared quickly.
- concurrent rendering — React ability to prepare several versions of the UI at once and to pause, resume or abandon rendering work so urgent updates are handled first.
Taught in
- Disposability, Dev Prod Parity And Logs — DevOps & Site Reliability Engineering
- Deployment Strategies: Rolling Updates — DevOps & Site Reliability Engineering
- Containers And Orchestration Context — DevOps & Site Reliability Engineering
- State with useState: Immutability And Asynchronous Batching — React 19 & Modern Component Architecture
- React Fiber Architecture: Work Units, Priority And Commits — React 19 & Modern Component Architecture
- Concurrent Mode: Interruptible Work And Lane Priority — React 19 & Modern Component Architecture