Simplifying Services with the Apache Brooklyn Catalog: The CF Brooklyn Service Broker and Plugin
summary
Apache Brooklyn exposes its YAML blueprints to Cloud Foundry via a Spring Boot service broker and a CLI plugin that use the Brooklyn Java client, persist mappings in Brooklyn, and add REST endpoints for create/delete, sensor and effector endpoints, and an is_running probe. The CLI’s cf brooklyn push can auto-add catalog entries, create services, substitute manifest values and bind them. Demos show a React cluster of size 3, a Mongo topology of 5 shards x 3 replicas, and a resize effector that grows a cluster to five nodes successfully; async and parameters API work remains.
AI-written summary · about
chapters (7)
- 0:00Introduction to Apache Brooklyn
- 3:34Service Broker for Cloud Foundry
- 8:25Demo of Brooklyn Catalog
- 12:22CLI Plugin for Brooklyn
- 16:14Multi-service Application Demo
- 23:40Summary and Future Plans
- 30:26Q&A Session
related talks
35mLearn to Develop a Service Broker in No Time
24mHow to Build Spring Services for Cloud-Native Platforms
25mService Brokers That Work for You!
06mThe New Inner Development Loop for the Cloud Service Broker
30mHow to Scale Single-Node Service Brokers with Subway
39mManaged CF-as-a-Service: An Operator's Cookbook
30mDeploying Cloud Foundry with BBL, BOSH 2.0 and CF-Deployment
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship