Getting Started & Migration
How can I run old and new engines side by side during migration?
Parallel dual-engine deployments offer a safe way to validate Catalyst during migration without disrupting live production workloads. Route a small subset of traffic to Catalyst while keeping most work on your existing production engine, log all outputs for systematic result comparison, and use regular shared monitoring to track performance across both systems. Note that observability is not an audit record, so you may need to perform manual cross-checks as needed.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Getting Started & Migration
What does a minimal but realistic durable agent look like when I first run Catalyst locally?
A realistic durable agent prototype that progresses from a call to an LLM through a conditional action to an API, illustrating automatic state persistence.
- Getting Started & Migration
How do I iterate quickly on durable agent logic without deploying to a shared cluster?
Use a local Dapr sidecar to execute and debug agent workflows, enabling a fast edit-run-debug cycle without remote dependencies.
- Getting Started & Migration
My agent is already built with LangChain/LlamaIndex. Can I add durable execution without a rewrite?
Wrap an existing agent’s entry point in a Catalyst workflow to gain durability without modifying framework internals, then progressively refactor.
