What's Cloud Foundry and why you want to use it
summary
Cloud Foundry is shown as a PaaS that actually does: developers run CF push, buildpacks detect runtime and produce a droplet, Diego cells run containerized instances, the gorouter load‑balances, Metron streams logs to a firehose, and a service broker provisions a MySQL instance which is bound via cf bind. Minimum working cluster size is 25–30 EC2 instances in the demo; scaling uses cf scale and deployments achieve zero‑downtime by mapping and unmapping routes.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:59What is Cloud Foundry
- 2:03Cloud native tech
- 3:49Microservices architecture
- 5:41Orchestration role
- 6:45Cloud Foundry value
- 7:32Dev and ops shift
- 8:17Cloud Foundry architecture
- 17:44Live demo: push app
- 23:28Connecting services
- 30:28Scaling applications in Cloud Foundry
- 30:50Why containers
- 32:41Zero-downtime deployments
- 40:51Q&A
related talks
25mCloud Foundry in Simple Terms: A Beginner's Journey
25mThe Essential Getting Started Guide to Cloud Foundry
31mWinning in Production
28mCloud Foundry 101 for Kubernetes Users
31mPut Your Money Where Your CF Is
43mHow Platforms Work
33mGive Cloud Foundry to your Company
31mNew Cloud Foundry Architectures and Features and their Performance Impact