How to Implement Loose Coupling with a SOA Architecture <p>I've been doing a lot of research lately about SOA and ESB's etc. </p> <p>I'm working on redesigning some legacy systems at work now and would like to build it with more of a SOA architecture than it currently has. We use these services in about 5 of our websites and one of the biggest problems we have right now with our legacy system is that almost all the time when we make bug fixes or updates we need to re-deploy our 5 websites which can be a quite time consuming process. </p> <p>My goal is to make the interfaces between services loosely coupled so that changes can be made without having to re-deploy all the dependent services and websites.</p> <p>I need the ability to extend an already existing service interface without breaking or updating any of its dependencies. Have any of you encountered this problem before? How did you solve it?</p>