 |
If we want to consume service, does it not make sense to have an easy, consistent and reliable way to do so? What are some of the capabilities of this consumption model that we would want? Naturally we would want a way to identify services, to create them, bind to them, and then clean then up once we are done. We need to do this at all stages of the software lifecycle, from development, test, QA and into production. If we could do this without the use of hard-coded credentials, YAML files and the like—all the better! A key capability of Cloud Foundry is that of the Service Broker—a simple and consistent way to access services that may be running on top of Cloud Foundry, controlled by Cloud Foundry or running totally independently of Cloud Foundry. In this week’s episode we examine the concept of the Service Broker, how it works, how you can build your own, and what it brings to the developer’s toolkit. Resources:
|
|
|
