什么是SOA（面向服务架构）？ [英] What is SOA (Service Oriented Architecture)?

问题描述

打电话给我一个巨魔，如果你想要的，但我是认真的 - 究竟是新的SOA趋势，比我在15年前建立的客户服务体系有什么不同？我不断听到的SOA，但我不知道它是如何比我们一直在做不同的。回到10年前，中，Y公司有多个客户端（多国语言）的交谈同样的服务。这不是XML（这是一个名为Microsoft DCOM的二进制协议），而且没有自动发现通过WSDL，但是没关系，因为阅读文档是很容易。我们的系统甚至开放在这个意义上，我们记录它足以让第三方谈谈我们的服务。我们不是开拓者 - 10年前我就知道每一个其他公司做同样的事情。
   唯一的区别我当时和现在之间看到的是，现在有在互联网上提供单一的服务，而在10年前，每个客户将举办自己的服务实例。但是，这不是一个架构问题 - 在服务的物理生命是透明的，使用该服务的人。

Call me a troll if you want, but I'm serious -- how exactly is the new SOA trend any different than the client-service architecture that I was building 15 years ago? I keep hearing SOA but I don't see how it's different than what we've always done. Back 10 years ago, ,y company had multiple clients (in multiple languages) which talked to the same service. It wasn't XML (it was a binary protocol called Microsoft DCOM) and there wasn't auto-discovery through WSDL but that's OK since reading the docs was just as easy. Our system was even "open" in the sense we documented it enough to allow 3rd parties to talk to our services. We were not pioneers -- every other company I knew 10 years ago was doing the same thing. The ONLY difference I see between then and now is that now there's a single service available on the internet, whereas 10 years ago, each customer would host his own instance of the service. But that's not an architecture issue -- where the service physically lives is transparent to anyone using the service.

那么究竟什么是SOA这比我们一直在做了多年不同？是SOA只是一个营销术语，再presenting，实际上已成为普遍的一个很久很久以前最好的做法？还是我缺少一些subtely到SOA这不同于我们所一直有做？

So what exactly is SOA that's different than what we've been doing for years? Is SOA simply a marketing term representing a best practice that actually became common a long long time ago? Or am I missing some subtely to SOA that's different than what we've been doing all along?

推荐答案

忘记XML。忘了WSDL。 SOA是不是可以买技术，虽然它经常销售的方式。

Forget about XML. Forget about WSDL. SOA is not a technology you can buy, though it's often marketed that way.

SOA的真正的问题是所有关于它的组织的。 SOA的关键是要避免的那些孤立的数据池，要么不跟对方在所有（因此经常重复数据）应用程序的巨大一堆，或仅在通过适配器层的效率低下，马车道或EAI系统。

The real point of SOA is all about IT organization. The point of SOA is to avoid having a huge bunch of "applications" that have isolated data pools and either don't talk to each other at all (and thus often duplicate data), or only in an inefficient, buggy way through adapter layers or EAI systems.

有关的大公司，这是一个严重的问题 - 他们有数百个独立的应用程序，没有得到充分整合的。有重复和不一致的数据随处可见，其结果是客户得到生气了，并真正赚钱的是丢失，因为计费部门保留，因为它是在订单跟踪取消发送取消订单和客户服务代表甚至无法找到订单发票系统，而不是计费系统

For large companies, this is a serious problem - they have literally hundreds of separate apps that are insufficiently integrated. There's duplicate and inconsistent data everywhere and the result is that customers get pissed off and real money is lost because the billing department keeps sending invoices for a cancelled order and the customer service rep can't even find the order because it's cancelled in the order tracking system, but not the billing system.

SOA应该由每一个应用程序从底层设计来解决这个高达标准化，跨洗车台的方式公布其服务，以便其他应用程序可以访问数据并没有复制它。

SOA is supposed to solve this by designing every app from the ground up to publish its services in a standardized, cross-platfrom manner so that other apps can access the data and don't have to duplicate it.

从商业角度看，这是非常可取的。 Buzzword的炒作和缩写汤仅仅是IT公司的企图套现的愿望。不幸的是，这有（MIS）导致许多人，包括CEO们相信，SOA是你可以买一个产品，它会神奇地让您的IT更加高效，而没有意识到这只会发生，如果您还重新组织整个IT（和相当也许是你的业务单位也一样）是SOA的兼容。

From a business perspective, this is highly desirable. The buzzword hype and the acronym soup is just IT companies' attempts to cash in on that desirability. Unfortunately, this has (mis)led many people, including CEOs into believing that SOA is a product you can buy and it will magically make your IT more efficient, without realizing that this will only happen if you also reorganize your entire IT (and quite possibly your business units as well) to be SOA-compatible.

这篇关于什么是SOA（面向服务架构）？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！