Endpoint Binding Strategy Examples

In this example, you are developing a single service that will be deployed multiple times with the same endpoint in a test environment before the service is deployed one final time to a runtime environment. The binding strategy could be a combination of service development binding and deployment binding.

Service development binding binds the service to the endpoint in a test environment; this setting is maintained through multiple iterations of test deployment. The service definition stores the binding information, eliminating the need to define the binding each time the package is created or each time the package is deployed in the test environment.

When the service is deployed to a runtime environment, the binding is set and maintained using deployment profile binding. Whenever the package is deployed using the runtime deployment profile, the runtime binding overrides the binding in the service profile.

In this example, you are developing multiple services that will be packaged together. The services will be reused for other packages as well.

Using a package profile binding strategy allows you to develop services independent of any binding settings and move management of binding to the package level. By using this strategy, binding is set in the package profile.

In this example, a single package is deployed to multiple servers, each using a different endpoint, or multiple packages are deployed to the same server.

The deployment profile binding allows you to bind to the endpoint a single time during deployment profile definition rather than for each service or for each package.