Skip to content

Decisions

0007 - Cache and write-behind

Architecture decision: Cache and write-behind

On this page

Date: 2026-06-09

Status: Accepted.

Context

Repeated settings reads and writes can put unnecessary load on the database.

Decision

We use local caches and coalesced writes for selected settings that users can resubmit. Critical state takes immediate persistence paths.

Consequences

A process failure before a flush can lose deferred writes, and cached reads can be stale. Callers must select a path appropriate to the data’s durability and consistency needs.

References

Cache, Batch, Modules repository.