vendor-documentation · locator & rights
Access storage; SQL in Durable Objects vs D1
Link and original paraphrase only; upstream rights retained.
Composition / PRODUCT DOSSIER
DODurable Objects + SQLite
Per-object SQL storage colocated with application logic.
Investigation: Can a Lexical editor collaborate through Yjs on Durable Objects? →
Cloud runtime · Not established · Hosted runtime; SQLite engine is public domainRevision 2026-09-14.1 · unreviewedNeeds recheck · recheck 2026-10-140 attestations · checked 2026-09-14
What we do not know yet · 2 open gaps
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applies to: 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.
Applicability, 1 recheck triggers & verification plan
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.
Excludes: Runtime verification; Workload benchmarks and cost comparisons; Unlisted extensions, service tiers and deployment configurations
Recheck when
- Upstream version, license, API, service plan or storage topology changes.
Needs recheck · due
Verification plan
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- For vector workloads, measure filtered recall against an exact-search baseline and record index settings.
Provenance & review
Testedknowhow database research
Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.
Revision 2026-09-14.1 · unreviewed · checked
0 attestations · Content: Unlicensed prototype; redistribution decision pending
Relational · Composition
Each object owns private storage. Application implements Worker routing and cross-object coordination.
Catalog components: SQLite ↗
Target sources: Durable Objects storage ↗
Capability claims · 5 / 17 sourced
Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.
Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.
Data model
SQL queriesYes
Explore SQL queries →
Queries tables through the object SQL API.
Consistency
Multi-record transactionsYes
Explore Multi-record transactions →
Provides transactional storage within one object.
Scope: No cross-object transaction guarantee is claimed.
Operations
Point-in-time recoveryYes
Explore Point-in-time recovery →
Provides point-in-time recovery for SQLite-backed object storage.
Architecture
Compute beside storageYes
Explore Compute beside storage →
Runs object code beside its attached SQLite storage.
Managed database servicePartial
Explore Managed database service →
Cloudflare hosts compute and storage.
Scope: Application must implement routing, object logic and additional database tooling.