Using the Theory of Constraints to Prioritize Applications for Migration to Cloud Foundry
summary
Uses the Theory of Constraints to find innovation bottlenecks in a portfolio and prioritize apps that directly limit business throughput, not just those that “fit” technically. Recommends initial filters (exclude packaged apps, hardware‑tied or business‑irrelevant apps), sizes slices for rapid wins (a retailer delivered five slices to production in four weeks), and migrates via the strangler pattern with circuit breakers, Eureka, CI/CD and buildpacks to go fast and safe while scaling teams and avoiding a migration factory.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:31Enterprise IT
- 1:44Processes
- 2:20Intentions
- 2:59Aging Applications
- 3:39Cloud Foundry is part of the solution
- 5:01Common stages in Cloud Foundry adoption
- 6:00Greenfield applications
- 8:22Application migration swamp
- 9:43Forget the main goal
- 10:52Application migrations of unusual size
- 11:56How do I choose the right application
- 13:06What not to migrate
- 16:26Application Migration Factory
- 17:37Theory of Constraints
- 19:35Innovation bottleneck
- 22:20Shadow IT
- 23:32Initial Filters
- 26:29Finding Innovation bottlenecks
- 27:09Strangler vine
- 29:25Reading Resources
related talks
01h 00mEvolving to Cloud Native
33mRe-thinking the journey to the cloud
32mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
45mContinuous Delivery and the Theory of Constraints
30mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
20mDeployment Strategies for Cloud Applications: Intel Case Study
26mSkilling Up: How to Effectively Grow a Cloud Foundry Organization - Steve Greenberg, Resilient Scale
43mSoftware Engineering Management at Scale with the Theory of Constraints