Dapr on Kubernetes and AKS
From Dapr fundamentals and a fast local development loop to AKS integration, building blocks and production operations.
Wolkwacht topic
Practical guidance for building and operating distributed applications with Dapr on Kubernetes and Azure Kubernetes Service.
Dapr moves recurring distributed-application concerns behind portable HTTP and gRPC APIs. This collection follows a practical path through service invocation, state, messaging, secrets, workflows, observability, security and day-two operations, with Kubernetes and AKS as the primary environments.
See the complete series roadmap for the planned publishing sequence.
Recommended entry point
The conceptual foundation for understanding Dapr's sidecar model, application building blocks and fit on Kubernetes and AKS.
Follow the thread
From Dapr fundamentals and a fast local development loop to AKS integration, building blocks and production operations.
Automatically updated
Production readiness starts where most tutorials end. Installing Dapr, deploying sidecars, and proving the building blocks are necessary milestones, but they do not answer the …
A Dapr-enabled application can work perfectly with one replica and still be unprepared for production. The sidecar may have no resource requests, every application may be able to …
A request can fail even when every Kubernetes pod is Running. The application may be waiting for a Dapr component, a retry may mask a slow dependency, or a call may reach the …
The first six parts of this series covered Dapr’s most familiar building blocks: service invocation, state management, and pub/sub. They solve application-to-application …
A synchronous request establishes a direct dependency: the caller pauses while the destination handles the task. This approach is suitable when an immediate response is required. …
Persisting a shopping cart often involves database-related tasks: choosing a client library, setting up a connection pool, managing credentials, serializing the model, retrying …