Modernize your ASPNET based systems using the Strangler Fig pattern
summary
Claims an incremental migration converts an ASP.NET 4.7.2 MVC app to .NET 6 using YARP reverse proxy as a facade and system.web adapters (RC) to share cookies, sessions and a serialized claims principal. A customer case takes about a year, routes static assets and APIs by pattern rewrites, and succeeds but surfaces real issues: machineKey/cookie decryption, cached assets, deployment entanglement of menu routes, and no Windows auth yet in adapters. Code is on GitHub.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:13Whats a Strangler Fig
- 5:58Routing
- 6:43Session State
- 7:45Jarp
- 9:43Facade
- 11:43System Web adapters
- 14:28Demo
- 15:43MVC application
- 18:26ASPNET Core configuration
- 20:22System Web Adapter configuration
- 25:26Sharing Session State
- 32:56Authentication
- 36:23Questions
related talks
01h 04mMigrate Your Legacy ASP.NET Projects to ASP.NET Core Incrementally with YARP
01h 00mOld to Gold: How to Modernize Your Legacy ASP.NET Apps Gradually
01h 03mTales from the .NET 8 Migration Trenches
49mFrom VB to Angular and Beyond Mastering Legacy Codebase Modernization
23mStranglerApplication pattern: a legacy frontend use case
58mModernizing an existing system to take a more domain-driven approach
11mThe monster under the bed - working with legacy code
01h 02mSolid ASP.NET Core
