# Durable Objects + SQLite

Per-object SQL storage colocated with application logic.

## Comparison target

Relational · Cloud runtime · Composition

Each object owns private storage. Application implements Worker routing and cross-object coordination.

Components: sqlite

Revision: 2026-09-14.1 · Review: unreviewed

Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

## Applicability

Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.. Each object owns private storage. Application implements Worker routing and cross-object coordination..

## Claims

- **yes · documented**: Queries tables through the object SQL API. [Durable Objects storage](https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/) Scope: Documented for this target; no runtime tests recorded.
- **yes · documented**: Provides transactional storage within one object. [Durable Objects storage](https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/) Scope: No cross-object transaction guarantee is claimed.
- **yes · documented**: Provides point-in-time recovery for SQLite-backed object storage. [Durable Objects storage](https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/) Scope: Documented for this target; no runtime tests recorded.
- **yes · documented**: Runs object code beside its attached SQLite storage. [Durable Objects storage](https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/) Scope: Documented for this target; no runtime tests recorded.
- **partial · documented**: Cloudflare hosts compute and storage. [Durable Objects storage](https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/) Scope: Application must implement routing, object logic and additional database tooling.

## Open questions

- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?

## Verification plan

1. Pin the target configuration and define workload fixtures, access and budget.
2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Last checked: 2026-09-14. Recheck by: 2026-10-14.

Content rights: Unlicensed prototype; redistribution decision pending.