何时使用 SOA(面向服务的架构) [英] When to use SOA (Service Oriented Architecture)

问题描述

我最近与我们的一位架构师进行了一次对话，他将他对 SOA 的使用总结为我们唯一会使用服务的时候是我们需要异步操作的时候，否则我们将使用直接访问数据存储"

I had a conversation with one of our architects recently and he summarized his use of SOA as "The only time we'll use services is when we need async actions otherwise we'll use go direct to the data store"

我考虑过这个说法，它似乎很合乎逻辑，因为服务在发布订阅模型中运行良好，但我想知道您应该在哪些其他场景中使用 SOA?

I thought about this statement and it seems fairly logical as services work well in a publish subscribe model, but I was wondering in what other scenarios you should be looking to use SOA?

推荐答案

我们向客户公开服务，因为他们不应该直接连接到数据源.

We expose services to our customers because they shouldn't be able to connect to the datasource directly.

我们向自己公开服务，因为使用 WCF 可以更轻松地将它们分布在不同的技术上.

We expose services to ourselves because it's easier to spread them over different technologies using WCF.

我们公开服务是因为我们对同一个数据源有不同的用户界面.当我们使用服务时，我们节省了三分之一的工作.

We expose services because we have different user interfaces for the same datasource. And when we use services we save a third of the work.

这绝不仅仅是因为异步操作.

It is never only because of the async actions.

这篇关于何时使用 SOA(面向服务的架构)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！