Skip to content

[Meta] Improvement program 2026 — comparison, roadmap & tracking #447

Description

@pathosDev

Tracking issue for the 2026 improvement program: framework comparison → gap analysis (deduplicated against the existing tracker) → roadmap. 37 new issues were opened as part of this program (#406#446); everything else referenced below already existed.

1. Where actor-ts stands (framework comparison)

Capability Akka 3 / Pekko Orleans Erlang/Elixir Proto.Actor Temporal/Restate Cloudflare DO actor-ts
Core actors + supervision ✅ (grains) partial
Cluster + sharding + singleton managed
Event sourcing + projections partial Mnesia basic ✅ (workflows) ✅ (5 backends)
CRDTs / distributed data ✅ (8 types)
Reliable delivery
Streams w/ backpressure Orleans Streams GenStage/Broadway ❌ → #147/#54
Durable timers/reminders ✅ (alarms) ❌ → #168
Saga / durable workflows ✅ (Akka 3) ❌ → #179/#88
AI-agent runtime ✅ (2025 pivot) via MS AF ✅ (headline) ❌ → #421 (flagship)
DevTools / observer UI commercial dashboard ✅ observer ✅ UI ❌ → #445
Browser/edge story ❌ → #446 (unique opportunity)
Multi-runtime TS-native SDK only Workers only ✅ Bun+Node+Deno

Verdict: ~95 % parity with the classic Akka core; the open gaps were almost all already ticketed here. The differentiators nobody else can copy cheaply: TS-native full stack on three runtimes, and (upcoming) durable AI agents + isomorphic actors.

2. Positioning

"The TypeScript-native actor runtime — and the durable AI-agent runtime for TS." Batteries included, dependencies excluded.

3. Dependency policy (binding — details in #419)

4. Documentation definition-of-done (binding — details in #420)

No feature is done without: concept guide (EN + DE), full JSDoc on public APIs, runnable example, HOCON config reference, CHANGELOG entry. Large modules (agents, jobs, client, devtools) additionally get their own docs chapter + example app.

5. Milestones (order, not version promises — versions are assigned at release cut)

M1 — Security hardening (first)

Foundation (land early, everything after inherits it):

Security triage of the open backlog, in waves — most urgent first: #110, #121, #126 + #136, #117 + #141, #406.

M2 — Performance & robustness

M3 — Packaging, DX & CI

M4 — Flagship: actor-ts/agents

M5 — Feature parity & patterns

Existing: #147 (streams subset first; #54 full DSL after), #168 (reminders), #179 + #88 (saga), #169 (placement), #170 (stateless workers), #156, #151, #159, #177.
New: #431 (jobs — after #168), #433 (DLQ), #434 (OpenAPI), #432 (presence).

M6 — DevTools & simulation

M7 — Isomorphic actors (browser & edge)

M8 — Integrations (continuous, demand-driven)

New: #437 (cloud brokers), #438 (persistence backends) — DONE, closed: MongoDB, DynamoDB, MS SQL, libSQL/Turso and Cloudflare D1 all shipped with the full journal + snapshot + durable-state trio, EN+DE docs and live integration suites; follow-ons split out as #490 and #491, #439 (lease backends), #440 (observability pack), #441 (Helm), #443 (Effect interop — parked), #444 (delta CRDTs — parked).
Existing same category: #15, #16, #72, #73, #74, #160, #4, #5.

6. Deliberately NOT re-ticketed (dedup)

Streams (#54/#147), reminders (#168), saga (#179/#88), virtual-actor features (#169#175), gen_statem/trap_exit/via-registry/RPC (#163#166), multi-DC (#149), simulation/time-travel/hot-reload/chaos/visualizer (#200#206), edge/browser (#209/#210/#215), Avro/Protobuf (#73), schema-registry client (#72), router strategies (#153/#154/#69), the code-quality catalog (#235#282), CRDT property tests (done), CI coverage restore (#325), ZeroMQ/STOMP (#15/#16), HTML sanitizer (#355), persistence robustness (#377#383, parallel session).

7. 1.0 criteria

M1–M3 complete; publint/attw/knip green; coverage floor restored to 89; bench gates holding; security backlog empty; API freeze + CHANGELOG discipline.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: highTop priority — high impact, plan next

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions