Articles for people who
ship the stack
Rewrites on React, Node.js, TypeScript and AI. A translated body is shown when it exists. If it does not, you see the English text and a note that says so.
Tagged: Concurrency
Why raising concurrency causes HTTP 429s: start rate and per-host limits
Raising worker count without shaping start rate and per-host caps creates bursts that trip 429s. Throughput comes from paced concurrency, backoff, and honest queue design.
16 min readCoordinate multi-tab uploads with the Web Locks API
Stop duplicate resumable uploads across browser tabs by replacing localStorage and BroadcastChannel hacks with navigator.locks and a React upload coordinator.
6 min readSerialize async work in JavaScript with a promise mutex
Serialize overlapping async work in JavaScript with a promise mutex: an AsyncLock chain runs requests FIFO so UI state stays ordered, no thread locks needed.
3 min readLearning Rust Through Ten Projects, from CLI Tools to Inference Services
A graded ladder of ten Rust projects, from a log-scanning CLI to a Redis clone, shell and inference service, and what each one teaches about memory, concurrency and failure.
11 min readSharing Memory Between Node.js Worker Threads with SharedArrayBuffer and Atomics
Why postMessage gives each Node.js worker a private copy, when SharedArrayBuffer is worth it, and how Atomics prevents lost updates and enables cross-thread waiting.
7 min readWaiting vs Computing: Concurrency and Parallelism in Node.js and Go
Runnable Node.js and Go examples that separate concurrency from parallelism, showing when promises suffice, when you need worker threads, and how goroutines differ.
8 min readPreventing Lost Updates in Node.js and MongoDB Under Concurrent Writes
Learn how atomic conditional updates, version-based optimistic locking, 409 responses and transactions stop concurrent MongoDB writes from silently discarding data.
9 min readOffloading CPU-Heavy Work in Node.js with worker_threads and Pools
Learn how Node.js worker_threads keep the event loop responsive: spawning workers, request-response messaging, transferable buffers, pools, and their pitfalls.
21 min readSeven Hidden Assumptions That Make JavaScript Fail Under Real Traffic
Learn which assumptions about types, retries, concurrency, response order, data volume, missing data and in-memory state break JavaScript code once it meets production.
14 min read
About these articles
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.