Modernizing Legacy Apps - Platforms and Strategies
summary
Cloud providers Microsoft and Amazon are actively paying to lift big on‑prem apps to their clouds, and real projects move decade‑old desktop systems (one tennis betting app replaces USB deploys across tournaments) to cloud landing with CI/CD, blob storage, Redis and JS‑heavy front ends. Options are lift-and-shift, replatforming or costly rewrites; decide by metrics like developer ramp time (weeks vs days), deployment automation, and bug‑fix time (one label change once took four hours). Prefer Isola et impera (isolate black‑box chunks, add APIs and integration tests); big rewrites sometimes fail catastrophically (Target, Lidl).
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 3:50Why software becomes legacy
- 10:01Modern app requirements today
- 12:09Lift and shift vs big rewrite
- 17:33Rep platforming challenges
- 20:29When to call for a big rewrite
- 26:14Microservices architecture trade-offs
- 32:51Isolate and conquer strategy
- 37:53From monolith to microservices
- 40:28Failure stories and lessons
related talks
30mThis Old App, a guide to renovating apps for the cloud
01h 00mEvolving to Cloud Native
48mContinuous Modernization
51mLegacy non-x86 modernization with
21mTransforming Legacy Systems: A DevOps Journey to Modernization
44mMigrating Legacy Applications to the Cloud
27mTech Modernization: A Cloud Migration
20mDeployment Strategies for Cloud Applications: Intel Case Study