You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to propose a new frontend for Turso that speaks DCB (Dynamic Consistency Boundary). It would live outside the core, like the SQLite and Postgres frontends. It would use Turso as an engine.
What is DCB?
DCB is a way to do event sourcing. An event is a fact that happened, for example "order placed".
DCB has two operations:
Append: "Add these events, but only if no new event matching my query was added after position X."
Read: "Give me all events that match this query."
The append rule keeps data consistent. It does not need one stream per entity.
The problem today
People build DCB on top of other databases. They use Postgres, key-value stores, or their own storage. This is hard because:
The consistency check needs custom code, such as stored procedures or retry loops.
Projections (read models) need extra systems to stay fresh.
The idea
Turso says it is "the LLVM of databases". An engine with different frontends is a good fit for DCB.
A DCB frontend would:
Write: offer a native append with the DCB condition. The engine checks it inside one transaction.
Read: stay as it is now. People use normal SQL on the same data.
Projections: use Turso materialized views, so projections update in real time.
DCB users get the full flow without any extra system. They send commands to the DCB frontend and query the results with SQL.
Questions for the team
Is a new frontend or extension a good fit for the Turso architecture?
Would you prefer this in the main repo, or as a separate project?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I want to propose a new frontend for Turso that speaks DCB (Dynamic Consistency Boundary). It would live outside the core, like the SQLite and Postgres frontends. It would use Turso as an engine.
What is DCB?
DCB is a way to do event sourcing. An event is a fact that happened, for example "order placed".
DCB has two operations:
The append rule keeps data consistent. It does not need one stream per entity.
The problem today
People build DCB on top of other databases. They use Postgres, key-value stores, or their own storage. This is hard because:
The idea
Turso says it is "the LLVM of databases". An engine with different frontends is a good fit for DCB.
A DCB frontend would:
appendwith the DCB condition. The engine checks it inside one transaction.DCB users get the full flow without any extra system. They send commands to the DCB frontend and query the results with SQL.
Questions for the team
All reactions