parallelism
Doing several pieces of work at the same time instead of one after another.
In more detail
True parallelism needs more than one CPU core or machine; code that is only concurrent takes turns on one core instead. Build tools run independent tasks in parallel, and test runners split suites across parallel workers. Parallelism only helps for work that does not depend on each other’s results.
Examples
In Kafka the partition count caps how many consumers in one group can read in parallel.In Node.js you get parallelism from the libuv thread pool, worker threads, child processes or the cluster module.Related terms
- partition — One of several independent ordered logs a message stream is split into, with each message routed to one partition by its key.
- consumer group — A set of consumers sharing one group ID that divide a topic's partitions between them so each partition is read by only one member at a time.
- partition assignment — The decision about which consumer in a group reads which partitions.
- task graph — A map of which build tasks depend on which others, used to decide what must run first and what can run at the same time.
- Promise.allSettled — A JavaScript function that waits for every promise in a list to finish and reports each one’s result, whether it succeeded or failed.
- Backend for Frontend — A small backend service built for one specific frontend, which gathers data from other services and shapes it exactly for that frontend’s screens.
- concurrency — Having several pieces of work in progress during overlapping periods of time, such as requests being handled at once.
- worker threads — The Node.js module for running JavaScript in parallel threads inside one process, each with its own V8 isolate and event loop.
- CPU core — One independent processing unit inside a CPU; a CPU with eight cores can run eight threads at literally the same time.
Taught in
- Where A Record Lands — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Forty Minutes To Start — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Monorepo Architecture: Workspaces & Turborepo — Production Full-Stack Engineering
- Unified Build Pipelines: Caching & Dependency Graphs — Production Full-Stack Engineering
- API Gateway & BFF Patterns: Backend-for-Frontend — Production Full-Stack Engineering
- End-to-End Testing with Playwright: Multi-Tier Suites — Production Full-Stack Engineering
- Topics, Partitions And Where A Record Lands — Apache Kafka & Event Streaming
- Consumer Groups And Partition Assignment — Apache Kafka & Event Streaming
- Watching Lag And Sizing Partitions — Apache Kafka & Event Streaming
- Worker Threads: worker_threads & SharedArrayBuffer — Node.js Internals & Backend Services
- Thread Pooling: Piscina & CPU-Bound Workload Pools — Node.js Internals & Backend Services
References
- Apache Kafka design: the consumer
- Turborepo: Running tasks
- Playwright: Parallelism
- Node.js: Worker threads