Loading video...

Video Failed to Load

Go Home

StreamDB - a reactive database in a Durable Stream. Designed for AI apps and agentic session state. You give it a Standard Schema. You get type-safe, multiplexed data sync into TANSTACK DB. Links in the 🧵

22,831 views • 6 months ago •via X (Twitter)

10 Comments

Electric's profile picture
Electric6 months ago

Blog post:

Electric's profile picture
Electric6 months ago

Agent sessions need state. Tool calls, messages, active generations. User presence, agent registration. In an ideal world you should just be able to declare a schema and have it work.

Electric's profile picture
Electric6 months ago

StreamDB does just that -- wrapping a Durable Stream with a Standard Schema to give you typed, reactive agent state.

Electric's profile picture
Electric6 months ago

You define your entity types — messages, presence, agents, whatever your session needs — as Standard Schema objects. StreamDB routes events into TanStack DB collections, with end-to-end type-safety.

Electric's profile picture
Electric6 months ago

Multiplexing is built in. It's reactive by design. It's durable by design. Everything is multi-user, multi-tab, multi-device and multi-agent out of the box. All reading and writing to the same stream.

Electric's profile picture
Electric6 months ago

Read the docs: Check out the demo app:

Electric's profile picture
Electric6 months ago

Deploy now on Electric Cloud:

Pedro Filho's profile picture
Pedro Filho6 months ago

@tan_stack how no one implemented this together with the cq from @mozilla ( yet?, to make a data sharing layer between agents real time?

Chat Data's profile picture
Chat Data6 months ago

@tan_stack Reactive session state is the part a lot of AI apps end up rebuilding badly. Schema first plus type safe sync makes the stack much easier to reason about. Curious how you handle replay and conflict resolution when multiple agents touch the same session state.

jordan's profile picture
jordan6 months ago

@tan_stack Whats different from durable state? Also, does this persist the data? I remember there was a large discussion of how persistence will be done in tanstack db. Anyways, very exciting. After trying all of the sync solutions out there, durable-* feels super clean

Related Videos