Skip to content

Cloud & DevOps

Where .NET meets ops. Containers (multi-stage, distroless, chiseled, AOT-friendly), Kubernetes for .NET (probes, graceful shutdown), Aspire as the modern cloud-native dev experience, the Azure essentials (App Service, Functions, Storage, Cosmos DB, Cache for Redis, Service Bus / Event Hubs, Key Vault, App Configuration, Monitor / App Insights, APIM, Container Apps / AKS, Entra ID / RBAC), Infrastructure-as-Code (Bicep / Terraform), the Azure CLI / azd toolbelt, CI/CD, and feature flags.

Topics (canonical order)

Why this order

Containers → K8s → Aspire moves from primitive to highest-level abstraction. Then a sweep through Azure-specific services in the order an engineer typically encounters them: hosting → containers → storage → data → cache → messaging → observability → identity → APIMIaCCLI. CI/CD and feature flags close as cross-cutting deployment concerns.

Cross-references

Coverage notes

This section covers the Azure surface a senior .NET dev typically navigates end-to-end.