ASP.NET Core in Production: Lessons Learned
summary
Adopts ASP.NET Core early for a distributed monolith and reports concrete outcomes: cleaned dead dependencies, ran the portability analyzer, retargeted projects to newer frameworks, and scripted dotnet CLI builds because TeamCity plugins are flaky. Migration proceeds in baby steps with mixed services and multi‑target tests, produces real perf gains for numeric workloads, and exposes breaking changes like the memory cache API. Deployment requires self-contained deployments decisions and pipeline rewrites around TeamCity and Octopus Deploy. Overall migration is doable and useful but demands ongoing maintenance and vigilance.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 7:15System overview
- 12:09Lessons learned
- 17:03Unexpected benefits
- 20:09Dont overestimate the benefits
- 22:41Baby steps
- 24:49Migration
- 26:29Painkiller
- 27:02Analysis
- 30:40Pipeline Changes
- 34:26Tools Resources
- 35:05Portability Tool
- 38:46Final Advice
related talks
45mDotNet Core in Production
49mTaking your .NET Core container solution from laptop to production
35m"ASP.NET Core DevOps approach using VSTS and Azure Deployment"
58mMicroservices at Scale - ASP.NET Core, Service Fabric, and Azure in production
54m12 Factor MicroServices
52mRoad to .NET 6: migration story of hope and despair
55mField Notes : .NET Core and Docker in Production
51mGet up to speed with DevOps using modern development practices