An executor runs the work it is handed. Tasks wait in a queue, a pool of workers picks them up one by one, and whoever submitted a task carries on without waiting. It separates asking for work from doing it.
Why "executors"
Submit a task and walk away: that is the contract of an executor. Java's ExecutorService, Python's ThreadPoolExecutor, and the async runtimes behind Rust services all share it. Work goes into a queue, a bounded pool of workers drains it, and the caller gets back a handle to the eventual result.
The idea reaches well past a single process. Spark runs its jobs on executors spread across a cluster, and Airflow hands scheduled tasks to executors that run them locally, on Celery, or on Kubernetes. Decouple the request from the run, cap the concurrency, keep the queue moving: the word describes the mechanism itself.
Contact
executors.si is for sale, privately. Contact for registration history and transfer terms.
The portfolio
misalignment.si, plus nine names for the layers of modern infrastructure, each offered privately.