InternalADRs
ADR-0010: UI Cache Integration Is Optional and Decoupled
Core emits neutral DbEvents; UI cache integration is provided via optional adapters.
Status
Accepted
Context
Different applications use different UI frameworks and caching strategies. The core library must not depend on a specific UI solution.
Decision
RippleDB:
- emits neutral
DbEvents from the write path - provides optional UI integration helpers
- does not couple core logic to TanStack Query or any framework
Alternatives Considered
- Built-in UI cache
- Framework-specific core APIs
Consequences
- Core remains portable
- UI integration requires explicit wiring
- Multiple UI adapters can coexist
ADR-0009: Performance Is Achieved via Batched Reads, Not Join-Based Reactivity
Avoid client-side join reactivity; batch point reads into bulk queries per tick.
ADR-0011: List Query Dependency Mapping Is Explicit (Registry-Based)
Use an optional registry to map list key prefixes to dependent entities for invalidation.