When a service has multiple endpoints, the binding names give users a hint as to the endpoint's function. As a best practice, consider adopting a naming convention for bindings that identifies service endpoints in a clear and consistent manner. (This practice is especially important if your consumer applications will be querying the registry to obtain a service endpoint run time.)

In the examples shown above, each binding name includes a suffix to indicate the environment in which the endpoint resides.

Keep in mind that binding names are derived directly from the port names in the service WSDL. Therefore, to produce bindings whose names conform to the particular naming scheme that you have adopted, you must assign the appropriate names to port definitions in the WSDL to begin with.

For example, to produce the binding names shown in the single-stage example described in Example of the Bindings for a Service in a Single-Stage Registry, the port definitions in the WSDL must look as follows.