Architecting .NET solutions in a Docker ecosystem
summary
Demo application that tracks video-game high scores uses .NET Core 3.0, multi-stage Dockerfiles, and Azure Container Registry to produce immutable images (example tag 2.4.8), then deploys to Kubernetes/AKS with a rolling update of three replicas for zero downtime. Local development uses Docker Compose or a local Kubernetes cluster via Docker Desktop. Secrets come from Azure Key Vault or user secrets, HTTP retries and circuit breakers use Polly with HttpClientFactory, and health endpoints drive readiness and liveliness checks. multi-stage Dockerfile Azure Container Registry rolling update with 3 replicas
AI-written summary · about
chapters (14)
- 0:00Intro
- 3:45Running containers on Linux
- 4:51Containers on Windows
- 8:14Demo application reference architecture
- 9:03Container workflow and lifecycle
- 14:07Docker image layers .NET Core MAERSK
- 16:09Build pipeline in Azure DevOps Contains steps to
- 26:10Hosting using cluster orchestrators
- 37:16Working with environments in .NET Core Bootstrapping environment variables
- 39:28Dealing with secrets in configuration Where would you leave sensitive data?
- 41:10Reading secrets from Azure Key Vault Available from Configuration in ASPNET Core
- 45:46Fault handling policies Use policy configurations
- 49:30Integrating health checks
- 50:33Zero downtime deployments
related talks
01h 00mBring your ASP.NET Core solutions to Kubernetes in Azure
01h 03mScaling Docker Containers using Kubernetes and Azure Container Service
52mBring your ASP.NET Core solutions to Kubernetes in Azure
01h 03mCloud Native .NET
01h 00mPractical Container Scenarios in Azure
58mMulti-container applications with .NET Core on Kubernetes
01h 07mDocker Containers on Azure - let me count the ways
35mRunning a DevOps Style Production Docker Cluster Using the Microsoft Platform