One strategy for achieving loose coupling is to use the service interface (the WSDL for a SOAP WEB Service) to limit this dependency, hiding the service IMPLEMENTATION from the consumer. Loose coupling can be addressed by encapsulating the service functionalities in a manner that limits the impact of CHANGES to the implementation on the service interface.

However, at some point you will NEED to change the interface and manage VERSIONING without impacting service consumers, in addition to managing multiple security constraints, multiple transports, and other considerations.

One strategy for achieving loose coupling is to use the service interface (the WSDL for a SOAP Web Service) to limit this dependency, hiding the service implementation from the consumer. Loose coupling can be addressed by encapsulating the service functionalities in a manner that limits the impact of changes to the implementation on the service interface.

However, at some point you will need to change the interface and manage versioning without impacting service consumers, in addition to managing multiple security constraints, multiple transports, and other considerations.