Reinventing the Way of Building a Core Software Product in a 50 Year Old IT Co
summary
Legacy .NET CPQ product migrates to Cloud Foundry on Azure with a 12‑week platform dojo (4 weeks setup, 8 weeks production hardening), pair programming, Concourse pipelines and Diego cells; monolith splits into ~39 microservices using .NET Core, Vue.js and OAuth, backed by ~120 VMs across dev and test, preparing a 3‑AZ production. Outcome: release cycle reduced to 2 weeks (from 6 months), MSSQL integration preserved, MVP nearing launch, main blockers are cultural (pairing, waterfall habits), not technology.
AI-written summary · about
chapters (7)
- 0:00Introduction and keynote
- 3:12Customer’s cloud readiness challenge
- 10:01Building the cloud platform foundation
- 17:58Refactoring the product for cloud
- 23:21People challenges in transformation
- 28:02Key lessons and takeaways
- 29:30Q&A and closing remarks
related talks
31mBuilding an Enduring Culture of Engineering Excellence
43mDesigning software in the cloud
32mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
13mKeynote: Dell's Internal Transformation Based on Cloud Foundry
31mHow Microsoft and Pivotal Partnered to Deliver Pivotal Cloud Foundry on Azure to Run Ford Pass
30mFord Motor Company’s Transition from Auto-Motive to Auto-Mobility
45mFrom 5 to 100 in Product Development team in just 5 years
13mKeynote: Leveraging Cloud Foundry for Development Efficiencies