Bindings make it easy to connect services together. They enable components of large-scale, multi-tier applications to interconnect in a virtual cloud deployment that can span hybrid clouds. Recently, Cloud Application Manager made bindings even more powerful. Now at deploy time, services can automatically detect dependencies — with the help of binding tags.
Binding tags boost complex deployments in a couple of ways:
- Dynamic bindings. Tagged bindings discover instance connectivity dynamically. They serve as an auto-discovery mechanism where instances with binding tags can automatically connect to other instances that match those tags.
- One to many bindings. Bindings can connect one or many services together, again, using tags. Previously, every connection required an exclusive binding. But that’s no longer necessary.
We’ll use an example to see how bindings work. Let’s suppose that an Nginx loadbalancer needs to detect freshly launched Node.js instances and automatically add them to its loadbalancing pool. We do three things to achieve this scenario. The first two are part of box automation:
Define binding variables
Configure bindings for your application
Tag bindings for instance connectivity
Step 1. Define Binding Variables
Bindings are defined as variables in box automation. In the Nginx loadbalancer box, for example, we defined that the binding can connect to instances of...