Considerations of a Practical Migration to Cloud Foundry
summary
SAP migrates a product from an IaaS to Cloud Foundry, replacing VM provisioning and custom schedulers with CF tasks and managed services (Elasticsearch logging, managed databases), and keeps one Java Spring Boot artifact deployed to both platforms to simplify rollback. Applications become 12‑factor: stateless, quick‑startup, graceful shutdown, config via env vars. Load and stress tests against production copy validate behavior; teams avoid refactoring during migration, aim for scale-to-zero dev environments and one artifact deployed to both platforms for easier debugging.
AI-written summary · about
chapters (8)
- 0:00Introduction and overview
- 1:07Why migrate to Cloud Foundry
- 3:13Application adaptation steps
- 7:54Key application changes needed
- 14:36Executing the migration process
- 20:34Next steps after migration
- 25:12Cultural perspective of migration
- 28:44Questions and answers
related talks
22mPushing the Limits: Cloud Foundry Runtime and Routing at SAP...
01h 12mInside spring.io: a Production Spring Reference Application
28mA Journey to the Center of the Cloud Foundry
12mCF Application Runtime Demo: Weighted Routing (Istio/Envoy), Multiple Custom App Ports...
26mThe State of Supply Chain Security in the Cloud Foundry Ecosystem
45mKeynote:
19mHow Did Our Garden Grow? Advances in the Cloud Foundry App...
32mThe Cloud Foundry Bits-Service Myth Buster!