Skip to content

[Feature] Additional persistence backends: MongoDB, DynamoDB, MSSQL, libSQL/Turso, Cloudflare D1 (umbrella) #438

Description

@pathosDev

Umbrella issue — one checkbox per backend; each backend lands as its own PR against this issue.

Rationale

Persistence currently ships in-memory, SQLite, Cassandra/ScyllaDB, PostgreSQL and MariaDB. Common stacks are missing; and the edge-oriented backends (libSQL/Turso, Cloudflare D1) directly enable the WASM/edge runtime ambition (#209).

Scope (checkboxes)

  • MongoDB (journal + snapshot store + durable state)
  • DynamoDB (journal + snapshot store + durable state)
  • MS SQL Server (journal + snapshot store + durable state)
  • libSQL / Turso (SQLite dialect over HTTP)
  • Cloudflare D1 (SQLite dialect over HTTP API)

Per backend: the full trio following the Postgres/MariaDB plugin pattern (schema bootstrap, optimistic concurrency, tagging where the store supports it — document a tagging-support matrix), integration test via container/emulator, docs page EN + DE.

Dependency policy (binding): drivers are optional lazy peerDependencies only. libSQL/Turso and D1 should be implemented SDK-free over their HTTP APIs via the built-in HttpClient where practical.

Documentation

Persistence docs: backend matrix update + one page per backend (EN + DE); CHANGELOG per backend.

Acceptance (per backend)

  • Journal/snapshot/durable-state contract test suite green against the real store (containerized); recovery + tagging behavior verified; no new hard dependency.

Relates

#71 (bulk wrap-legacy migration), #209 (edge runtimes), #377#383 (persistence robustness — land first). Dependency policy #419. Improvement program M8.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions