Durable Objects, Workers - New Durable Object namespaces must use the SQLite storage backend
If your account does not already have a key-value (KV) backed Durable Object namespace, you can no longer create new ones. New Durable Object namespaces must use the SQLite storage backend , which…
Read the full articleYou might also wanna read
Implementing a Durable Execution Engine Using SQLite for Persistent Workflows
Lately, there has been a lot of excitement around Durable Execution (DE) engines. The basic idea of DE is to take (potentially long-running)
sqlite-utils 4.0rc1 released with migration support and nested transactions
sqlite-utils is my combined Python library and CLI tool for working with SQLite databases. It provides an extensive set of higher-level oper
Exploring Persistence and Durability in Key-Value Databases
I've been working on a complex multi-model database for a few weeks now, and recently I took time to simplify and test out an idea I had on
sqlite-utils 4.0 released with database schema migrations, nested transactions, and compound foreign keys
This morning I released sqlite-utils 4.0, the 124th release of that project and the first major version bump since 3.0 in November 2020. In
SQLite is All You Need for Durable Workflows - Blog
SQLite is All You Need for Durable Workflows - Blog obeli.sk/blog/sqlite-...
SQLite as a Viable Alternative for Durable Workflow Execution
DBOS recently argued that Postgres is all you need for durable execution: if you already trust your database, you do not need a separate orc

Comments
Sign in to join the conversation.
No comments yet. Be the first.