GoKawiilNew open-source library brings Durable Objects model to Postgres, SQLite, MySQL
A developer released Solid Objects, an open-source library that replicates the Durable Objects programming model—one identity, one state, one ordered mailbox per object—without requiring a dedicated vendor runtime or daemon. Instead, it runs directly on databases developers already operate, including SQLite, PostgreSQL, and MySQL. The release follows the creator's frustration with vendor lock-in and unpredictable metered billing tied to existing Durable Objects platforms.
GoKawiil's interpretation of the reporting above, not reported fact.
Durable Objects style architectures are popular for stateful serverless apps, but tying them to a single vendor creates cost unpredictability and painful migration costs, as illustrated by a developer billed $34,000 for a runaway process with zero users. By turning the pattern into a library that runs on standard databases, Solid Objects removes the need for a separate daemon or proprietary backend, lowering operational overhead and vendor risk for teams needing durable, ordered object state.
- Solid Objects reimplements the Durable Objects model as a library rather than a hosted service.
- It runs on existing SQLite, PostgreSQL, or MySQL databases, avoiding extra daemons or vendor lock-in.
- The project responds to real pain points: unpredictable metered billing and forced migrations tied to single-vendor durable object platforms.
Designing Data-Intensive Applications by Martin Kleppmann — If durable state, single-writer objects, and Postgres-backed consistency are your daily puzzles, Kleppmann's book is the definitive tour of the tradeoffs behind them. It walks through replication, consensus, and storage engines in plain language, so the design choices in libraries like Solid Objects make a lot more sense.
See Designing Data-Intensive Applications by Martin Kleppmann on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.Source: solidobjects.dev — Lucas Carlson, 2026-09-08
Published there as: “Open Source Durable Objects for Postgres”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.