Undo for Service Brokers
summary
Demonstrates an implementable “undo” for Cloud Foundry service brokers by hacking create with -c clone_from to recreate deleted instances; uses asynchronous provisioning, caches instance-name→UUID mappings, and stores per-instance backups in S3 with continuous archiving (WAL) so restores duplicate backups to a new instance ID. Prototype is dingo-postgresql and runs without a CF plugin, scoped to the same space for simple auth. Also notes the CF surface is sparse (≈81 service endpoints, ≈172 CLI commands) so this is a pragmatic workaround that works.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:18For the love of databases
- 8:47Implement broker
- 17:22Continuous archiving
- 24:05User Experience
related talks
25mService Brokers That Work for You!
27mDistributed Service Bundles for Cloud Foundry - Krishanu Biswas, SAP
20mHow to Build a High Performance App Using Cloud Foundry and Redis
35mBuilding a Production Grade PostgreSQL Cloud Foundry Service
49mHave you ever wondered, how a cloud platform works?
31mBuilding the Dragonfly Operator from Scratch
46mTransform your development workflow with thin cloning
44mWhat's New in Cloud Foundry Volume Services