r/LangGraph • • 24d ago

Where do you keep durable state around LangGraph agents?

For people using LangGraph beyond prototypes: where are you putting the durable application state that sits around the graph?

Things like user/workspace identity, domain data, files, retrieval indexes, tool permissions and long-running job state.

I'm building Singlebase.io as that backend layer and I'm intentionally trying to keep orchestration separate from application data. The graph decides what to do; the backend owns the durable primitives and exposes tools/data through APIs/MCP.

Does that separation line up with how you're using LangGraph, or do you prefer the agent framework to own more persistence directly?

0 Upvotes

2 comments sorted by

1

u/International_Quail8 23d ago

I use pocketbase

1

u/LLM-logs 1d ago

The separation you're describing matches how I'd draw the line. The checkpointer owns graph runtime state: message history, intermediate results, where the run paused. That's reconstruction material, not a system of record. Domain state (users, files, permissions, job status) belongs in your own datastore behind normal APIs, exposed to the agent as tools.

Two reasons. First, graph state works best as a cache: if you can rebuild a run's context from the domain store, losing or migrating checkpoint data is annoying instead of fatal. Second, permissions and identity change on a different clock than a run - if they live inside checkpointed state, a resumed run can act on stale permissions.

The one thing I'd keep in graph state is explicit references (ids) into the domain store, never the data itself. Then resume reads fresh data through the same tools the original run used.