Building Momentum Toward Cloud Foundry
summary
Argues that Cloud Foundry app runtime (via CF push and buildpacks) accelerates developer flow while container runtime is better for third‑party images; recommends refactoring a legacy factory app into a stateless widget scanner with externalized state, environment variables for config, and logging to stdout as an event stream. Emphasizes three priorities: dependencies configurations logs. Gives a concrete failure: centralizing config caused a 30–45 minute outage when many clients reloaded, so start small, map dependencies, and automate pipelines.
AI-written summary · about
chapters (5)
- 0:00Introduction and speaker background
- 2:26App vs container runtimes explained
- 11:58Moving legacy applications to Cloud Foundry
- 21:50Building momentum in your org
- 26:13Summary and Q&A
related talks
06mAccelerate Application Delivery with a Cloud-Native Mindset
31mDeploying Microservice Architectures with Cloud Foundry
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications
29mRocking the Lattice: A New Path for Cloud Foundry Applications
30mThe transformative power of modern applications
42mBeyond CF Push - Managing Large Microservice Applications like a BOSH
51mMoving at the Speed of Thought
41mEmbracing Architectural Challenges in the Modern .NET World