The Subtle Art of Keeping your Broker Multi-platform Compatible
summary
Explains concrete failure modes and mitigation for brokers using the Open Service Broker API: three deployment patterns—alongside the platform, on-top apps, and a central control plane—and why networking gaps block cross-cloud registrations. Calls out auth reality: Basic auth remains the interoperable option until the declarative authentication flow lands. Gives two real pitfalls: service/plan names must be CLI-friendly (underscores fail in Kubernetes’ service catalog) and DB column defaults break string limits across Postgres vs MySQL; recommends CI tests against each target platform.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:23Goals
- 1:29Agenda
- 2:02Who?
- 8:57On top of the platform
- 9:27Hosted
- 10:32Networking
- 13:52Authentication
- 22:21Takeaways
- 25:45References
related talks
36mSIG Service-Catalog Intro – Doug Davis, Michael Kibbe & Morgan Bauer
39mPlatform Engineering as a (Community) Service
34mSteward, the Kubernetes-Native Service Broker
38mMicroservices, a bittersweet symphony
32mHow Might You Platform: Avoiding Traps Before It's Too Late
36mApplication Architecture Patterns
27mDon’t put all of your APIs in one cloud
41mArchitecting Kubernetes-Based Internal Developer Platforms: Essential Patterns...