Running a DevOps Style Production Docker Cluster Using the Microsoft Platform
summary
A mission‑critical .NET Core system runs in a Kubernetes cluster on Azure built with Visual Studio 2017 and Visual Studio Team Services, instrumented with Application Insights and paging into VictorOps; background workers use Refit + HTTPClientFactory and a hosted service loop that applies Polly retry + circuit‑breaker policies (ten retries with exponential backoff), SignalR notifies the SPA, and an outbox pattern buffering ensures delivery during failures; automated ARM templates enable regional failover that reduced a real outage to minutes.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:55WHAT IS DEVOPS
- 1:11DevOps is the union of people, proce products to enable continuous deliver
- 7:45ABSENCE OF ERRORS IS NOT
- 14:25DEMO: TELEMETRY
- 15:21PATTERNS FOR RES
- 16:03TROUBLE WITH SINGLE PC FAILURE
- 17:15DEGRADED PERFOI
- 20:57DEMO: RESILIENCY
- 28:09DEMO: PATI
- 29:48WHAT COULD POSSIBLY GO
related talks
37mRunning a real-world mission-critical system on Azure
34mRunning a DevOps style production Docker cluster using the Microsoft platform
49mTaking your .NET Core container solution from laptop to production
52mBring your ASP.NET Core solutions to Kubernetes in Azure
40mDevOps and Kubernetes in VSTS on Azure and Beyond
58mMicroservices at Scale - ASP.NET Core, Service Fabric, and Azure in production
01h 03mScaling Docker Containers using Kubernetes and Azure Container Service
55mArchitecting .NET solutions in a Docker ecosystem
