executor-architecture

Durable execution with DBOS and PostgreSQL relies on structured workflows, event buses, and task queues to guarantee exactly-once processing. The architecture separates API, services, and implementation layers to maintain state consistency.

A tRPC and PostgreSQL workflow executor structures components into API routes, core services, DBOS workflows, and data stores. This modular layering enforces clear interaction patterns between client requests and durable backend processing.

To set up local development mode for a DBOS executor, navigate to the executor package and enable local execution using the ENABLE_DBOS_EXECUTION environment variable. This bypasses production deployment requirements.

Use DBOS production mode for deployed environments requiring durable exactly-once execution guarantees. Use local development mode to test architecture layers, event buses, and tRPC routes without full infrastructure overhead.

Key components of a durable workflow executor include the ExecutionWorkflow, ExecuteFlowAtomicStep, ServiceFactory, and DBOSEventBus. These files manage state transitions, service instantiation, and event-driven communication.

Yes, the executor architecture supports tRPC routes to bridge client and server interactions. A dedicated TRPC router exposes administrative and execution endpoints over the durable DBOS workflow layer.