Getting Started

Guides

Adapters

Reference

Internal

RippleDB Architecture Purpose & Scope Package Structure & Dependency Rules Core Principles Core Data Model Sync Model Query Model & Invalidation Performance via Batching UI Integration (Optional)Comparisons & Out-of-Scope

Architecture Decision Records (ADRs)ADR-0001: Local Storage Is the Source of Truth ADR-0002: Replication Is Log-Based (Append-Only), Not State-Based ADR-0003: Field-Level LWW Using Hybrid Logical Clocks (HLC)ADR-0004: Deletes Are Modeled as Tombstones ADR-0005: Distinguish Row Queries from List Queries ADR-0006: Row Queries Are Invalidated Precisely by ID ADR-0007: List Queries Use Broad Invalidation and Rerun ADR-0008: Sorting Requires the Same Invalidation Strategy as Filtering ADR-0009: Performance Is Achieved via Batched Reads, Not Join-Based Reactivity ADR-0010: UI Cache Integration Is Optional and Decoupled ADR-0011: List Query Dependency Mapping Is Explicit (Registry-Based)ADR-0012: CRDTs Are Explicitly Out of Core Scope ADR-0013: Complexity Is Rejected in Favor of Predictability

Packages

ADR-0014: Monorepo Package Structure and Layering ADR-0015: Core Package Must Be Pure and Dependency-Minimal ADR-0016: store-* and db-* Packages Own Backend/Runtime Dependencies ADR-0017: UI Integrations Live in bind-* Packages ADR-0018: Package Names and Intended Responsibilities ADR-0019: Strict Dependency Graph Between Packages

InternalADRs

ADR-0019: Strict Dependency Graph Between Packages

Enforce a strict package dependency graph to prevent architectural erosion.

Status

Accepted

Context

Even with multiple packages, accidental imports can break layering and portability.

Decision

We enforce the following dependency graph:

@rippledb/core
- depends on nothing (or only tiny pure deps)
@rippledb/client and @rippledb/server
- depend on @rippledb/core
@rippledb/store-*
- depend on @rippledb/core (and optionally @rippledb/client interfaces)
@rippledb/db-*
- depend on @rippledb/core (and optionally @rippledb/server interfaces)
@rippledb/bind-*
- depend on @rippledb/core (for types like DbEvent) and on their UI library
- must not be required by core/client/server

Alternatives Considered

Free-form dependency structure
Everything depends on everything

Consequences

Prevents architectural erosion
Enables use in many environments
Requires linting or workspace constraints (recommended)

ADR-0018: Package Names and Intended Responsibilities

Canonical package set and naming: store-* (client truth), db-* (server persistence), bind-* (UI bindings).

On this page

Alternatives Considered