Serve pre-generated static JSON for hot paths #15

Closed
opened 2026-07-01 00:57:51 +00:00 by manlycucumber · 1 comment
manlycucumber commented 2026-07-01 00:57:51 +00:00 (Migrated from github.com)

Problem

The runtime must prefer pre-generated static JSON when it exists, returning it directly without invoking Core, so hot paths are as cheap as a static file read.

Acceptance criteria

  • When a static file exists for the canonical key, the runtime serves it without calling Core.
  • The static response carries the same envelope, headers, and data-version as the dynamic path.
  • A missing static file cleanly falls through to the dynamic path.
  • Static-vs-dynamic parity is covered by a test for the same key.

Notes

Static and dynamic responses for the same key must be byte-identical.

## Problem The runtime must prefer pre-generated static JSON when it exists, returning it directly without invoking Core, so hot paths are as cheap as a static file read. ## Acceptance criteria - [ ] When a static file exists for the canonical key, the runtime serves it without calling Core. - [ ] The static response carries the same envelope, headers, and data-version as the dynamic path. - [ ] A missing static file cleanly falls through to the dynamic path. - [ ] Static-vs-dynamic parity is covered by a test for the same key. ## Notes Static and dynamic responses for the same key must be byte-identical.
manlycucumber commented 2026-07-03 05:50:35 +00:00 (Migrated from github.com)

Delivered in #135 (squash-merged to develop).

Delivered in #135 (squash-merged to `develop`).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Directorium/Api#15
No description provided.