Systems

Every systems story.

2 stories across the archive, newest first.

#01 · 6 min

Durable execution: why long-running agents need a workflow engine

A durable execution engine persists the result of every side-effecting step as an event. If the worker crashes, another worker replays the history, skips the steps already done, and carries on from where it stopped. For agents that call slow, paid LLM APIs and tools, that turns crashes from expensive into boring.


Why you ·You already run Temporal next to LangGraph at HivePro. Knowing exactly what replay does (and why workflow code must be deterministic) is the difference between a resilient agent platform and mysterious non-determinism errors in production.

Open the deep dive: Durable execution: why long-running agents need a workflow engine
#01 · 5 min

Postgres + pgvector hybrid search as agent memory

Vector search finds passages that mean the same thing; keyword search finds exact names, error codes and IDs. Postgres can do both: built-in full-text search and the pgvector extension. Run both queries and merge the ranked lists, for example with reciprocal rank fusion, to get memory that handles both kinds of question.


Why you ·Hybrid RAG is already part of your HivePro stack, and doing it inside Postgres builds directly on the Postgres internals you're learning. It's also a cheap memory layer for Susanoo before you need a dedicated vector database.

Open the deep dive: Postgres + pgvector hybrid search as agent memory