Today we’re excited to show off our Habitat Open Service Broker reference implementation.
The Open Service Broker (OSB) project is an industry-wide collaboration to enable service consumption through a simple, secure, API-driven model. Using it, you can bridge between applications and services running on different clouds and platforms, allowing your application developers to request the service their application needs, and then having the broker supply that service and provide back credentials, in a consistent and reliable way.
For example, if you are running stateless microservices within a federated, cross-cloud Kubernetes cluster, and you wanted your application to be able to leverage a large distributed database service that you had running on bare metal, off cluster, for performance reasons, you could use the Open Service Broker to make that database available as part of a service catalog, and then have your applications connect to it from within the Kubernetes cluster -- or wherever they may be running -- with a simple command.
Habitat and the Open Service Broker are a great pairing in multiple dimensions. If you are using Habitat to automate the building and management of a catalog of distributed services for your development teams, Open Service Broker is an excellent way to do that, and it has been designed in partnership with popular enterprise platforms such as Kubernetes, CloudFoundry, and OpenShift. Continue to use Habitat to continuously build and ship your applications and services, run those services wherever fits your business best, and use Open Service Broker as the intelligent glue so that your consumers don’t need to worry about where and how the services they call are being run.
For example, a developer deploying applications to CloudFoundry -- either natively or built with Habitat -- can call out to a Habitat Open Service Broker maintained by her Operations team to easily request a service she needs. The Habitat Open Service Broker will receive that request, and fulfill it using a Habitat package in the topology the developer wants, on the infrastructure the Operations team has decided is the best fit (in our video demo below, this is a Kubernetes cluster, but it can be extended to the best infrastructure for the job). The developer’s application receives back the necessary service information to connect to and use the service she requested.
Additionally, you can follow the same mechanism to integrate your Habitat built applications with other Open Service Broker providers, such as Azure or Google’s, to do the same when there are cloud hosted services you would like to provide to your consumers. Open Service Broker is a great way to provide a rich array of services to your users.
On Friday, awesome Kinvolk team member Indradhanush Gupta showed how to use the Habitat Open Service Broker that he and Lili Cosic have been working on. It shows deploying services on a Kubernetes cluster via the OSB, but following this pattern you could deploy to other infrastructures as well using Habitat packages.
- Ask and answer questions on the Habitat forums
- Chat with the Habitat Community on Slack
- Learn more about Habitat
- Habitat Open Service Broker on GitHub
- Habitat Open Service Broker demo on Kubernetes
- Open Service Broker API
- Kubernetes And The Open Service Broker Make Multi-Cloud A Reality
- Connect your applications to Azure with Open Service Broker for Azure
- Introducing Kubernetes Service Catalog and Google Cloud Platform Service Broker: find and connect services to your cloud-native apps