DevOps Paradox DOP 326: Stop Reinventing The Wheel - Use Dapr Instead
Nov 26, 2025
Mark Fussell, co-founder of Dapr and Diagrid, previously a Microsoft engineer, discusses the need for simplifying microservices. He delves into how Dapr was created to eliminate repetitiveness in developing distributed systems by providing standardized APIs. The conversation also explores Dapr's evolution from a Microsoft project to a CNCF graduate, its support for durable workflows, and integration with AI. Mark highlights its multi-language SDKs and practical first use cases, demonstrating how Dapr enhances developer productivity while managing complex infrastructure.
AI Snips
Chapters
Transcript
Episode notes
Stop Rebuilding Distributed Patterns
- Dapr codified common distributed-systems patterns so teams stop rebuilding the same foundational plumbing.
- It exposes standardized APIs for service discovery, messaging, state, and security to speed development.
Abstract Infrastructure With Component Swaps
- Use Dapr's component model so your code calls stable APIs while the platform swaps underlying infra like Kafka or SNS.
- Change only component configuration to move between clouds without rewriting application code.
Modernizing A Monolith With PubSub
- DataGalaxy split translation work out of a monolith using Dapr PubSub and state store to process documents asynchronously.
- The new service loaded state, translated documents, wrote results back, and notified the original app via messaging.