Skip to content

roadmap.md

Latest commit

 

History

History
58 lines (51 loc) · 3.05 KB

roadmap.md

File metadata and controls

58 lines (51 loc) · 3.05 KB

Roadmap

The roadmap is the only forward-looking document in the maintained docs. It records the current support boundary and work outside the current implementation. Shipped changes live in ../CHANGELOG.md; current user behavior lives in User Guide.

Supported Now

  • macOS and Linux on x86_64 and aarch64.
  • Zig 0.16.0 as declared by build.zig.zon.
  • Threaded HTTP/1.1 server with per-request runtime isolation and decoded Content-Length or Transfer-Encoding: chunked request bodies.
  • Restricted JS/TS/TSX handler execution through zigts.
  • WebSocket gateway support with parsed peer close-code metadata.
  • The five core zigttp commands: init, dev, test, expert, deploy.
  • Local self-contained deploy artifacts with default-on attestation.
  • Compile-time checks for response paths, Result and optional handling, state isolation, active specs, flow properties, contracts, and module policy.
  • 22 built-in zigttp:* virtual modules listed in Virtual Modules.
  • Optional Studio and edge runtime builds via -Dstudio and -Dedge.

Current Limitations

  • Hosted cloud deploy is not part of the current CLI surface. deploy builds a local binary; account, grant, remote review, and provider-control-plane flows are not documented as supported user workflows.
  • The runtime uses the threaded HTTP server path. The evented std.Io networking path is not a supported request backend.
  • Handlers receive raw multipart/form-data bodies. Parse multipart bodies in handler code or behind a virtual module once one exists.
  • Native JIT code has a per-runtime-context soft cap; when the cap is exceeded at a JIT compile safe point, compiled function pointers are cleared and the context's native code pages are released.
  • Windows is not supported.

Planned Work

  • Land production FaaS table stakes before hosted deploy claims: per-request deadlines, graceful shutdown, health/readiness probes, structured JSON logs, panic isolation, and per-handler memory caps.
  • Finish the engine<->runtime boundary refactor by routing runtime calls through a strict facade, exposing stable runtime-facing engine types, and splitting zruntime.zig by concern without changing ownership semantics.
  • Keep near-term module work limited to table-stakes gaps: multipart decoding and fetch resilience. Cloud-adapter modules stay in a separate evaluated track.
  • Keep zigttp help --all, packages/zigts/src/builtin_modules.zig, and packages/modules/module-specs/ as the sources of truth for CLI and module docs.
  • Add server-level rate limiting only if the standalone server becomes a first-class unproxied deployment target; application limits are currently handled with zigttp:ratelimit.
  • Promote hosted deploy only after the control-plane path has CI smoke coverage and user-facing commands are present in default docs.
  • Defer VM-loop dedupe until the FaaS hardening, engine facade, and measurement gates are stable. The standalone plan lives in Deferred VM Loop Dedupe Plan.