Using Service Brokers to Manage Data Lifecycle
summary
A Cloud Foundry service broker provisions on‑demand test copies by cloning production VMs on AWS, creating an AMI snapshot, booting a new instance, assigning an elastic IP, running a sanitize script that zeroes credit cards, and returning bindable credentials to apps; demo moves a dataset of 430,000 rows via the async broker API, lets apps bind without tickets, and then terminates the instance and cleans up snapshots on cf delete, proving the pattern works end‑to‑end.
AI-written summary · about
chapters (12)
- 0:00Introduction to data challenges
- 0:48The problem with data copies
- 2:55The need for realistic testing
- 3:41Traditional data acquisition
- 4:32Challenges in data curation
- 5:51Service brokers for data management
- 6:52Demo: Provisioning a data copy
- 8:51Demo: Sanitizing data
- 13:29Demo: Verification and cleanup
- 16:17Benefits of the approach
- 18:51Implementing the solution
- 23:06Q&A and closing remarks
related talks
25mService Brokers That Work for You!
35mLearn to Develop a Service Broker in No Time
06mThe New Inner Development Loop for the Cloud Service Broker
30mOn-Demand Data Services with Cloud Foundry - Maria Ntalla & Simon Jones, Pivotal
30mHow to Scale Single-Node Service Brokers with Subway
05mYou Got Terraform in my Service Broker
39mManaged CF-as-a-Service: An Operator's Cookbook
18mHow we Migrated to the V2 Cloud Foundry Service Broker