What Not to do When Building Service Brokers
summary
Recommendation: implement full Open Service Broker API with community spec checkers and use existing libraries like brokerapi or the Open Service Broker client; run brokers over HTTPS with trusted certs and handle TLS termination points; store binding credentials in CredHub instead of returning plaintext env vars; avoid shared-instance noisy‑neighbor failures by enforcing quotas, careful plan sizing or choosing on‑demand instance provisioning; note one-off off‑spec flags (like force‑delete) can help but risk portability and platform support.
AI-written summary · about
chapters (6)
- 0:00Introduction to service brokers
- 5:38Running brokers securely over HTTPS
- 8:11Fully implementing the OSB spec
- 13:13Securing service binding credentials
- 18:32Multi-tenancy pitfalls in brokers
- 22:42Summary and key takeaways
related talks
40mOpen Service Broker 101: That Extra Something
30mHell Freezes Over: The New Reality of Open Cloud Services and the OSBAPI - Josh McKenty, Pivotal
49mSecure System Integrations
26mBuilding Scalable Microservice APIs From The Beginning
26mOpen Banking and Open Insurance: The Role of APIs and Microservices
57mHow Do I Secure My Micro-Services?
31mBoF: Security Best Practices in Cloud Foundry
15mREST APIs for partners, what’s the catch when applying best practices