如何实现松耦合以SOA架构 [英] How to Implement Loose Coupling with a SOA Architecture

问题描述

我最近一直在做大量的调查研究关于SOA和ESB的等。

I've been doing a lot of research lately about SOA and ESB's etc.

我的工作，现在在重新设计工作的一些遗留系统，并希望用更多的是SOA架构比它目前拥有的构建。我们对我们网站的5和我们现在所拥有的与我们的传统系统的最大问题之一使用这些服务是几乎所有当我们做出错误修复和更新，我们需要重新部署我们的5个网站可以是一个时间相当耗时的过程。

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.

我的目标是使松散耦合的，这样可以改变用户服务之间的接口，而无需重新部署所有相关的服务和网站。

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.

我需要扩展已经存在的服务接口不破坏或更新任何依赖关系的能力。以前任你遇到过这个问题吗？你是怎么解决的？

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?

推荐答案

我建议在寻找一个不同的样式也许你至今为止做的服务。认为彼此使用事件协作，而不是请求/响应服务。我一直在使用这种方法具有多年的成功的一个很大的不同的垂直行业的客户。我已经写了不少关于这些主题在过去的4年。这里有一个地方，你可以上手：

I suggest looking at a different style of services than maybe you've been doing so far. Consider services that collaborate with each other using events, rather than request/response. I've been using this approach for many years with clients in various verticals with a great deal of success. I've written up quite a bit about these topics in the past 4 years. Here's one place where you can get started:

的 http://www.udidahan.com/2006/08/28/podcast-business-and-autonomous-components-in-soa/

希望有所帮助。

这篇关于如何实现松耦合以SOA架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！