Engineer tested, manager approved: Migrating Windows/.NET services to Linux
summary
Campaign Monitor migrates legacy .NET Framework microservices to .NET Core on Linux using Docker and AWS ECS, running a two‑week spike with three engineers then a 6–8 months rollout. Portability Analyzer and the ICanHasDotNet dependency scanner flag required library upgrades; runtime uses Kestrel/libuv and the .NET Framework compatibility shim where necessary. 78 original reckless services reduce to 31 migrated; EC2 bill for hosts drops from ~$145k to ~$15k after packing and removing infra, with some tooling and async/namespace headaches.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:43Reckless microservice framework
- 5:44Twe-Three Software Generations
- 6:43How do I deploy a change?
- 6:53How does path routing work?
- 7:56Reckless microservices framework
- 9:23Three Generations
- 14:53What doesn't port to .NET Core?
- 18:10Ask for something small
- 34:34Reckless framework - infrastructure
- 35:09Getting support for cleanup projects
related talks
01h 00m20 year old cloud native apps with .NET
36mLegacy code - lessons learned during migration (...)
41mTaming .NET Framework legacy WebApi
01h 02m.NET from the ground to the cloud
44mHow Real is this Cross Platform .NET Thing Really?
58mUpgrade any .NET applications with the latest .NET stack.
01h 00mBrave New .NET
46mTales from the NET 8 Migration Trenches