Dapr in Production
What happens to my Dapr state store and pub/sub configurations when moving to Dapr Ops Dashboard?
Your application code using Dapr state store and pub/sub building blocks remains unchanged when moving to Dapr Ops Dashboard. Dapr Ops Dashboard manages the control plane but does not replace your external state stores or message brokers. You configure component connections as before, and Dapr Ops Dashboard handles sidecar discovery and authentication. Self-hosted Dapr requires you to manage these connections directly, while Dapr Ops Dashboard adds centralized configuration management.
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.
