Have you ever wondered, how a cloud platform works?
summary
Cloud Foundry runs production metadata on six PostgreSQL databases with the cloud controller DB dominating latency; a CI API performance suite plus production heat maps find slow endpoints and regressions. Rewriting ORM patterns and SQL DSL queries cuts a service-plans endpoint from ~30s to ~3s (10x improvement), schema work migrates event IDs to bigints with a three-step zero-downtime process, and a Postgres planner quirk — max_parallel_workers causing paralysis — forces disabling parallel plans on one deployment.
AI-written summary · about
chapters (16)
- 0:00Introduction to Cloud Platform
- 1:03Problem Statement for Developers
- 2:28What is Cloud Foundry?
- 6:03Core Concepts of Cloud Foundry
- 8:54How Cloud Foundry Works
- 10:44Live Demo of CF Push
- 12:07Cloud Foundry Components
- 13:31Cloud Controller and Its Database
- 16:47ORM Performance Pitfalls
- 20:48Performance Optimization Strategies
- 23:17Dynamic Query Challenges
- 27:16Schema Migration Insights
- 33:06Postgres Setup for Cloud Foundry
- 35:16Hyperscaler Database Tuning
- 37:07Postgres 11 to 15 Migration
- 41:19Q&A Session
related talks
35mBuilding a Production Grade PostgreSQL Cloud Foundry Service
27mCloud Foundry Compared with Other PaaSes
20mTaking Cloud to Extremes: Scaled-Down, Highly-Available, and Mission-Critical
48mCloud Foundry - your PaaS on OpenStack
20mHow to Build a High Performance App Using Cloud Foundry and Redis
43mPostgreSQL in the cloud: Theory and Practice
20mNavigate Postgres Cloud Paths: Kubernetes, IaaS, or DbaaS
40mBut can you really run your app on 2 clouds at the same time?