Actor-Web Lab · Week 1

JavaScript concurrency and actor mailboxes

Move through three layers without blending them: conceptual JavaScript queues, Node.js event-loop phases, and Actor-Web's actor-scoped scheduling. Predict the next location before advancing.

Projection
Layer: Question: Model:

Scenario code

    Before you advance

    Projection, not profiler: the diagrams explain ordering and ownership. They do not display a real process trace or every host implementation detail.

    Source mapping: Actor-Web's Node path uses setImmediate, awaits one actor delivery at a time, and yields after 100 successful deliveries when work remains. Failed deliveries are dequeued but do not currently advance that successful-delivery counter.

    Safety: blocking, starvation, and CPU-heavy scenarios are simulated. Use only the workbook's bounded experiments in a disposable local process.