Islands based multithreading
Worker pools and shared workers joined to your app through one
shared-memory fabric. Contracts share fixed-layout
SharedArrayBuffer state across threads; work is offloaded
via task commands and state reactivity.
npm install @atolljs/coreUI where it belongs, work where it belongs
One contract, every thread
Worker pools
Typed task dispatch over lazily-spawned workers. Call a method, get a promise.
Shared-memory contracts
Fixed-layout SharedArrayBuffer state, declared once and identical on both threads.
Cross-thread reactivity
observe, watch, and task state subscribe on either side of the boundary.
Worker-rendered islands
Whole framework trees committed off the main thread, replayed as DOM ops.
Five frameworks, five workers, one page
Every card below is a running micro-frontend: a real React, Vue, Solid, Svelte, or Angular component rendering inside its own dedicated worker. Clicks, timers, and state all live off the main thread; only DOM mutation ops cross back.
Micro-frontends without the plumbing
Typed contracts
defineSharedMemory and defineIslandContract declare the wire once. Both threads type-check against it, and payloads validate at the boundary.
Any framework, or none
One op protocol carries React, Vue, Solid, Svelte, and Angular trees side by side, plus imperative proxy-DOM apps. The shell never imports another framework.
Topology per mount
Dedicated worker, shared client, or nested sub-worker: the mount call decides, the app doesn't change. The demos put all three on one page.
Remote MFEs
Worker bundles can live on another origin, versioned and cached like any asset. The contract module is the only import the host needs.
postMessage plumbing, no serialization guesswork.
Declare the contract once, and both threads speak it.
Want to dig in?
Package docs ./consumer/
Consumer guide for @atolljs/core: install, quickstart, public API, framework bindings (React, Vue, SolidJS, Svelte, Angular, Next.js), worker islands, and hosting headers.
Blog ./consumer/blog/
Facades Over Threads: why Atoll exists, the problems it solves, and how its facades make worker interop look like ordinary components and services.
Internals docs repo → docs/
Architecture and internals as in-repo markdown: contract schema, fixed-layout memory, worker pool and task dispatch, reactivity, shared workers, the islands engine, cross-origin isolation.