Dapr in Production
Can I migrate existing Dapr OSS applications to Diagrid Catalyst without rewriting code?
Yes, Catalyst is designed for drop-in compatibility with existing Dapr applications. Your Dapr building block APIs—state, pub/sub, service invocation, workflows—remain unchanged. Migration typically involves updating the Dapr control plane to Catalyst’s managed version and configuring workload identity via Diagrid’s console or API. No application code changes are required, though you may need to adjust deployment manifests to reference Catalyst’s sidecar injection. Catalyst also supports existing state store and pub/sub component configurations.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Dapr in Production
What production responsibilities appear after adopting Dapr OSS?
After adopting Dapr OSS, production teams become responsible for operating the runtime safely across real environments.
- Dapr in Production
How is managed Dapr different from self-managed Dapr OSS?
Self-managed Dapr OSS means the organization runs and operates Dapr itself, including installation, upgrades, certificates, monitoring, and.
- Dapr in Production
What enterprise requirements should a Dapr platform satisfy?
An enterprise Dapr platform should satisfy requirements around reliability, security, operations, observability, support, and deployment control.