How we Migrated to the V2 Cloud Foundry Service Broker
summary
AppDirect replaces a proprietary V1 broker with the Cloud Foundry V2 service broker, implementing the three concrete APIs: catalog API, service API and binding API. Migration keeps existing accounts and data intact, runs V1 and V2 side‑by‑side, and takes about one to two weeks to rewire connectors; flip from V1 to V2 is seamless after Pivotal switches. Production marketplace already exposes roughly 20 services through the new broker.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 2:51Cloud Foundry service broker evolution
- 5:22Service broker API structure
- 8:31Adding service broker to Cloud Foundry
- 9:37Migration to V2 service broker
- 12:05Benefits of service brokers
- 13:53Q&A session
related talks
35mLearn to Develop a Service Broker in No Time
26mUsing Service Brokers to Manage Data Lifecycle
06mThe New Inner Development Loop for the Cloud Service Broker
25mService Brokers That Work for You!
30mHow to Scale Single-Node Service Brokers with Subway
24mHow to Build Spring Services for Cloud-Native Platforms
30mOn-Demand Data Services with Cloud Foundry - Maria Ntalla & Simon Jones, Pivotal
05mYou Got Terraform in my Service Broker