0Pricing
Node.js Backend Development Bootcamp · Lección

Compartición de memoria con SharedArrayBuffer y Atomics

Coordine hilos sobre memoria compartida mediante Atomics para evitar copiar búferes grandes y prevenir condiciones de carrera.

Compartición de memoria con SharedArrayBuffer y Atomics es una lección gratuita de Node.js Backend Development Bootcamp en CoddyKit. Esta es la lección 3 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Node.js Backend Development Bootcamp, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Node.js Backend Development Bootcamp incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

Why Shared Memory?

When you spin up a Worker in Node.js and call postMessage, the data you send is copied using the structured clone algorithm. For small messages that is fine, but for a large numeric buffer (millions of bytes) copying wastes CPU and memory.

  • SharedArrayBuffer lets multiple threads read and write the same block of memory with zero copying.
  • Atomics gives you safe, race-free operations on that memory.

This lesson shows how to coordinate threads over shared memory in a CPU-bound backend job.

ArrayBuffer vs SharedArrayBuffer

An ArrayBuffer is owned by one thread. When transferred to a worker, the sender loses access to it. A SharedArrayBuffer (SAB) is different: passing it to a worker shares the same backing store, so both threads see each other's writes.

You never read raw bytes directly. Instead you wrap the buffer in a typed array view such as Int32Array or Float64Array.

const sab = new SharedArrayBuffer(16);
const view = new Int32Array(sab);

console.log(view.length);
view[0] = 42;
console.log(view[0]);
console.log(sab.byteLength);

Passing a SAB to a Worker

To share memory, create the SharedArrayBuffer in the main thread and send it via postMessage. Unlike a normal buffer, a SAB is shared (not transferred), so both sides keep using it.

The worker wraps the same SAB in its own typed array view. No copy happens.

const { Worker, isMainThread, workerData } = require('worker_threads');

if (isMainThread) {
  const sab = new SharedArrayBuffer(4);
  const view = new Int32Array(sab);
  view[0] = 100;
  new Worker(__filename, { workerData: sab });
} else {
  const view = new Int32Array(workerData);
  view[0] += 1;
  console.log('worker sees', view[0]);
}

The Race Condition Problem

Plain reads and writes on a shared view are not safe when multiple threads touch the same slot. A statement like view[0] += 1 is really three steps: read, add, write. Two threads can interleave and lose updates.

  • Thread A reads 5, Thread B reads 5.
  • Both compute 6 and write 6.
  • Two increments happened, but the value only went up by one.

This is a classic data race. The fix is Atomics.

Atomics.add for Safe Counters

Atomics.add(view, index, value) performs read-modify-write as a single indivisible operation. No other thread can interleave, so increments are never lost.

Other useful methods: Atomics.sub, Atomics.and, Atomics.or, and Atomics.load / Atomics.store for plain reads and writes that are guaranteed visible across threads.

const sab = new SharedArrayBuffer(4);
const counter = new Int32Array(sab);

Atomics.store(counter, 0, 0);
Atomics.add(counter, 0, 5);
Atomics.add(counter, 0, 3);

console.log(Atomics.load(counter, 0));

Splitting CPU Work Across Threads

Imagine summing a huge array of integers, a CPU-bound task that would block the event loop. With shared memory you store the data once and let several workers each process a slice, writing partial results into a shared output slot via Atomics.add.

Because the input lives in a SharedArrayBuffer, you never copy the dataset to each worker. They all read the same bytes.

Compare-and-Exchange

Atomics.compareExchange(view, index, expected, replacement) writes replacement only if the current value equals expected, and returns the value that was there. This is the building block for lock-free algorithms and simple spinlocks.

Use it to claim a slot exactly once: if the swap succeeds, this thread won the claim.

const sab = new SharedArrayBuffer(4);
const slot = new Int32Array(sab);
Atomics.store(slot, 0, 0);

const prev = Atomics.compareExchange(slot, 0, 0, 1);
console.log('previous value was', prev);
console.log('claimed:', prev === 0);

const again = Atomics.compareExchange(slot, 0, 0, 1);
console.log('second claim succeeded:', again === 0);

Blocking with Atomics.wait

Sometimes a worker must pause until another thread signals it. Atomics.wait(view, index, expectedValue) blocks the calling thread while the slot still holds expectedValue. It returns 'ok', 'not-equal', or 'timed-out'.

  • Atomics.wait only works off the main thread (it would freeze the event loop otherwise).
  • Atomics.notify(view, index, count) wakes waiting threads.

This gives you a true thread barrier without busy-looping.

Notify to Wake Workers

The producer thread updates the shared slot with Atomics.store and then calls Atomics.notify to wake any thread parked in Atomics.wait. The order matters: change the value first, then notify.

In a real backend job this is how a coordinator releases all workers at once to start a phase, or signals that input is ready.

const { Worker, isMainThread, workerData } = require('worker_threads');

if (isMainThread) {
  const sab = new SharedArrayBuffer(4);
  const signal = new Int32Array(sab);
  Atomics.store(signal, 0, 0);
  new Worker(__filename, { workerData: sab });
  setTimeout(() => {
    Atomics.store(signal, 0, 1);
    Atomics.notify(signal, 0, 1);
  }, 50);
} else {
  const signal = new Int32Array(workerData);
  Atomics.wait(signal, 0, 0);
  console.log('worker released, value =', Atomics.load(signal, 0));
}

A Complete Parallel Sum

Here is the full pattern in one runnable file: a shared input buffer, a shared result slot, and two workers that each sum half the data and atomically add their partial into the result. The main thread waits for both to finish.

Notice the input is never copied; both workers read the same SharedArrayBuffer.

const { Worker, isMainThread, workerData } = require('worker_threads');

if (isMainThread) {
  const N = 1000;
  const dataSab = new SharedArrayBuffer(N * 4);
  const data = new Int32Array(dataSab);
  for (let i = 0; i < N; i++) data[i] = i + 1;

  const resultSab = new SharedArrayBuffer(8);
  const result = new Int32Array(resultSab);
  Atomics.store(result, 0, 0);
  Atomics.store(result, 1, 0);

  let done = 0;
  const ranges = [[0, N / 2], [N / 2, N]];
  for (const [start, end] of ranges) {
    const w = new Worker(__filename, { workerData: { dataSab, resultSab, start, end } });
    w.on('exit', () => {
      if (++done === ranges.length) {
        console.log('total =', Atomics.load(result, 0));
      }
    });
  }
} else {
  const { dataSab, resultSab, start, end } = workerData;
  const data = new Int32Array(dataSab);
  const result = new Int32Array(resultSab);
  let local = 0;
  for (let i = start; i < end; i++) local += data[i];
  Atomics.add(result, 0, local);
}

Practical Cautions

Shared memory is powerful but easy to misuse. Keep these rules in mind:

  • SharedArrayBuffer only stores numbers. To share strings or objects you must encode them (for example with TextEncoder into a Uint8Array).
  • Always use Atomics for any slot more than one thread might write; mixing plain writes and atomic writes reintroduces races.
  • Reserve a fixed slot for synchronization flags and document its index.
  • Use shared memory only when copying is a real bottleneck; for most messages plain postMessage is simpler and safe.

Quick Check

You have several worker threads incrementing one shared counter stored in an Int32Array backed by a SharedArrayBuffer. Which approach keeps the count correct under concurrency?

Recap

You learned how to coordinate Node.js worker threads over shared memory:

  • SharedArrayBuffer shares one backing store across threads with no copying; wrap it in a typed array like Int32Array.
  • Plain += on a shared slot causes data races; use Atomics for any concurrently written slot.
  • Atomics.add, Atomics.load, Atomics.store, and Atomics.compareExchange give race-free reads, writes, and lock-free claims.
  • Atomics.wait (off the main thread) plus Atomics.notify let threads block and signal without busy-looping.
  • Reach for shared memory only when copying large numeric buffers is a real bottleneck.

Preguntas frecuentes

¿La lección «Compartición de memoria con SharedArrayBuffer y Atomics» es gratis?

Sí — el texto completo de «Compartición de memoria con SharedArrayBuffer y Atomics» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Node.js Backend Development Bootcamp, actualiza a CoddyKit PRO. El curso de Node.js Backend Development Bootcamp incluye 4 lecciones en total.

¿Qué aprenderé en «Compartición de memoria con SharedArrayBuffer y Atomics»?

Coordine hilos sobre memoria compartida mediante Atomics para evitar copiar búferes grandes y prevenir condiciones de carrera. Practicas Node.js Backend Development Bootcamp con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar Node.js Backend Development Bootcamp?

No se requiere experiencia previa. Node.js Backend Development Bootcamp en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 3 de 4.

¿Cuánto tiempo toma la lección «Compartición de memoria con SharedArrayBuffer y Atomics»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de Node.js Backend Development Bootcamp?

Sí. Cada lección de Node.js Backend Development Bootcamp incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

  1. Por qué el event loop se bloquea con trabajo limitado por CPU
  2. Creación de Worker Threads e intercambio de mensajes
  3. Compartición de memoria con SharedArrayBuffer y Atomics
  4. Construcción de un grupo de workers reutilizable para aumentar el rendimiento
← Volver a Node.js Backend Development Bootcamp