feature-toggles

Persists per-feature enabled/disabled state in the read_global_feature_state table and exposes a set write-handler plus list/registered query-handlers so operators can flip features at runtime without redeploying. Each API instance keeps an in-memory GlobalFeatureToggleRuntime snapshot (initialize it via createFeatureToggleRuntime, pass a () => runtime accessor to createFeatureTogglesFeature) that the dispatcher gate reads on every request; a toggle-cache-sync multi-stream projection with delivery: "per-instance" syncs the snapshot across instances whenever a toggle-set event is appended.

How it fits

What this feature needs to run (Requires, top) and the write commands it provides (Provides, bottom).

flowchart TB
  n_feature_toggles["feature-toggles"]
  subgraph how_provides["Provides"]
    n_cmd_feature_toggles_write_set(["set"])
  end
  n_feature_toggles --> n_cmd_feature_toggles_write_set

Provides — write commands this feature registers (dispatch them through the command bus):

• feature-toggles:write:set

Dependencies

• Requires: none
• Activation: always on (not toggleable)