blocks|key|55674|text|忘了XML吧。忘掉WSDL吧。SOA不是一种你可以买到的技术，尽管它经常以这种方式销售。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|55675|SOA的真正意义在于IT组织。SOA的要点是避免大量具有隔离数据池的“应用程序”，这些应用程序要么根本不相互通信(因此经常是重复数据)，要么只是通过适配器层或EAI系统以一种低效、有缺陷的方式进行通信。|55676|对于大公司来说，这是一个严重的问题--他们有数百个独立的应用程序，但没有足够的集成。到处都是重复和不一致的数据，其结果是客户被激怒了，真正的钱被损失了，因为计费部门一直在为取消的订单发送发票，而客服代表甚至找不到订单，因为它在订单跟踪系统中被取消，而不是在计费系统中。|55677|SOA应该通过从头开始设计每个应用程序，以标准化、跨平台的方式发布其服务，以便其他应用程序可以访问数据，而不必复制它，从而解决这个问题。|55678|从业务角度来看，这是非常可取的。时髦的炒作和首字母缩写soup只是IT公司利用这种可取之处的尝试。不幸的是，这(错误地)导致许多人(包括CEO)相信SOA是一种可以购买的产品，它将神奇地提高您的it效率，而没有意识到这只有在您重新组织整个IT+(很可能还有您的业务部门)以与SOA兼容的情况下才会发生。|55679|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

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

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 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.

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.

blocks|key|2753773|text|我认为SOA既是一个营销术语，也是现有解决方案的集成，其理念是我们销售服务，而不是销售整个软件或机器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2753774|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think SOA is both a marketing term and an integration of existing solutions with the idea of instead of selling the whole software or machine, we sell the services.

blocks|key|2753787|text|Neal+Ford对SOA有很多强烈的观点。你可能会发现他的观点很有趣。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2753788|Tactics+vs.+Strategy+(SOA+&+The+Tarpit+of+Irrelevancy)|offset|length|2753789|Standards+Based+vs.+Standardized+(SOA+&+the+Tarpit+of+Irrelevancy)|2753790|Tools+&+Anti-Behavior+(SOA+&+the+Tarpit+of+Irrelevancy)|2753791|Rubick's+Cubicle+(SOA+&+the+Tarpit+of+Irrelevancy)|2753792|The+Triumph+of+Hope+over+Reason+(SOA+&+The+Tarpit+of+Irrelevancy)|2753793|Guerrilla+SOA+(SOA+&+The+Tarpit+of+Irrelevancy)|2753794|entityMap|0|LINK|mutability|MUTABLE|url|http://memeagora.blogspot.com/2009/01/tactics-vs-strategy-soa-tarpit-of.html|1|http://memeagora.blogspot.com/2009/01/standards-based-vs-standardized-soa.html|2|http://memeagora.blogspot.com/2009/02/tools-anti-behavior-soa-tarpit-of.html|3|http://memeagora.blogspot.com/2009/03/rubicks-cubicle-soa-tarpit-of.html|4|http://memeagora.blogspot.com/2009/03/triumph-of-hope-over-reason-soa-tarpit.html|5|http://memeagora.blogspot.com/2009/04/guerrilla-soa-soa-tarpit-of-irrelevancy.html^0|0|0|1I|0|0|0|1U|1|0|0|1J|2|0|0|1E|3|0|0|1T|4|0|0|1B|5|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@$D|1D|E|1E|1|1F]]|A|$]]|$1|H|3|I|5|6|7|1G|8|@]|9|@$D|1H|E|1I|1|1J]]|A|$]]|$1|J|3|K|5|6|7|1K|8|@]|9|@$D|1L|E|1M|1|1N]]|A|$]]|$1|L|3|M|5|6|7|1O|8|@]|9|@$D|1P|E|1Q|1|1R]]|A|$]]|$1|N|3|O|5|6|7|1S|8|@]|9|@$D|1T|E|1U|1|1V]]|A|$]]|$1|P|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]|Z|$5|S|T|U|A|$V|10]]|11|$5|S|T|U|A|$V|12]]|13|$5|S|T|U|A|$V|14]]|15|$5|S|T|U|A|$V|16]]]]

Neal Ford has many strong opinions regarding SOA. You might find his viewpoint interesting.

<a href="http://memeagora.blogspot.com/2009/01/tactics-vs-strategy-soa-tarpit-of.html" rel="nofollow noreferrer">Tactics vs. Strategy (SOA &amp; The Tarpit of Irrelevancy)</a>

<a href="http://memeagora.blogspot.com/2009/01/standards-based-vs-standardized-soa.html" rel="nofollow noreferrer">Standards Based vs. Standardized (SOA &amp; the Tarpit of Irrelevancy)</a>

<a href="http://memeagora.blogspot.com/2009/02/tools-anti-behavior-soa-tarpit-of.html" rel="nofollow noreferrer">Tools &amp; Anti-Behavior (SOA &amp; the Tarpit of Irrelevancy)</a>

<a href="http://memeagora.blogspot.com/2009/03/rubicks-cubicle-soa-tarpit-of.html" rel="nofollow noreferrer">Rubick's Cubicle (SOA &amp; the Tarpit of Irrelevancy)</a>

<a href="http://memeagora.blogspot.com/2009/03/triumph-of-hope-over-reason-soa-tarpit.html" rel="nofollow noreferrer">The Triumph of Hope over Reason (SOA &amp; The Tarpit of Irrelevancy)</a>

<a href="http://memeagora.blogspot.com/2009/04/guerrilla-soa-soa-tarpit-of-irrelevancy.html" rel="nofollow noreferrer">Guerrilla SOA (SOA &amp; The Tarpit of Irrelevancy)</a>

blocks|key|2542342|text|让我使用集成地狱中著名的替罪羊:电信公司。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2542343|早在20世纪90年代，手机公司在我所在的社区就已经供过于求，几乎和90年代中期放松通信管制带来的长途经销商一样多。随着时间的推移，贝尔大西洋公司成了Verizon的巨头，吞并了一家又一家公司(至少还有一家Baby+Bell)。这些公司中的每一家都有技术到位，在塔楼中，在交换设备中，在计费系统中，这些技术彼此完全不兼容。|2542344|因此，公司说，好吧，我们有这些模型来做生意，让我们以WSDL/SOAP/XSD的形式为我们的所有技术提供一个友好、一致的面孔--我们今天拥有的每种语言和系统都可以与此接口！慢慢地，但肯定的是，该公司正在使其所有系统都能够报告功能，为加载和计费目的而被询问，并公开给未来的远见者以尚未考虑到的方式进行利用。|2542345|任何人都可以构建SOA客户端。任何有wget和文本编辑器的人。任何人都可以解析结果(XML)。|2542346|这就是与过去的客户机/服务器架构的根本不同之处。前几天，我刚刚和一个人讨论了如何将基于Cobol和Smalltalk的系统连接到SOA架构。这是一个很容易解决的问题。请告诉我，您的DCOM系统也可以这样说。|2542347|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Let me use the famous whipping boy of Integration Hell: Telco.

Way back in the 90's, cell phone companies were plethoric in my neighborhood, almost as plentiful as the long distance resellers made possible by the communications deregulation of the mid 90's. Well, time goes on, and Bell Atlantic becomes the powerhouse that is Verizon, and swallows up company after company (and at least one Baby Bell). Every single one of these companies has technologies in place, in towers, in switching equipment, in billing systems that are COMPLETELY incompatible with one another.

So the company goes off and says, okay, we have these models for how we do business, let's put a friendly, consistent face on ALL of our technology in the form of WSDL/SOAP/XSD - every language and system we have today can be interfaced to this! Slowly but surely, the company is making all of it's systems capable of reporting on capabilities, being interrogated for load and billing purposes, and exposed for future visionaries to exploit in manners that haven't been accounted for yet.

Anyone can build a SOA client. Anyone with wget and a text editor. And anyone can parse the results (XML).

That is what's fundamentally different from past client/server architectures. I was just talking the other day to someone about interfacing Cobol and Smalltalk based systems to SOA architectures. That's an easy problem to solve. Tell me you can say the same for your DCOM systems.

blocks|key|2753826|text|SOA只是一种设计服务的方式，其中的模块之间通过“”进行通信。就是这样，现在的下一个问题是:什么是“服务”，它与常规的“方法”有什么区别？|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2753827|服务是执行单个原子业务操作的操作。这种原子性使得它可以从许多模块中高度可重用的。然后，一个复杂的业务操作就是以特定顺序调用这些服务的集合。|2753828|SOA与特定的技术无关，只是一种特定的设计方式。|2753829|entityMap^0|P|18|0|0|1X|0|0|O|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

SOA is nothing but a way of design, in which the modules comunicates with each others through "services". It is just that, and now the next question is: what is exactly a "service" and what is its difference with a regular "method"??

A service is an operation that performs a single, atomic business operation. This atomicity make it highly reusable from many modules. Then a complex business operation is just the orchestation of the invokation of many of these services in a specific order.

SOA has nothing to do with specific technology, is just an specific way of designing.

blocks|key|2542390|text|对我来说，当企业希望将涉及公共领域的一组不同的应用程序集成到一组针对单个数据源操作的可互操作的服务中时，就会产生面向服务的体系结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2542391|以一家新成立的公司为例，该公司有一项软件/软件套件的想法，我看不出一家公司如何从一开始就采用面向服务的体系结构。首先，每个解决方案(很可能演变为服务，使得它可能变得可互操作)都应该寻求孤立地解决其问题空间。|2542392|也许在企业功能或套件的路线图中，每个解决方案在解决方案完成并进入服务时成为可互操作的服务。为此，开发团队可能会采用模块化/面向组件的方法来构建解决方案(最终服务)，以便更容易将解决方案作为服务包含在面向服务的体系结构中。|2542393|在现有的软件孤岛将成为面向服务的体系结构中的可互操作的服务的情况下，该方法允许软件项-其可以是分布式的并且可以用不同的语言编写-经由所展示的API和/或公共协议(例如，一种Web服务)和通用数据格式(例如，XML)进行通信。|2542394|SOA是一种方法或想法。它不是一个框架或工具。当WDSL和EJB被丢弃时，这通常会被遗忘……因为SOA的概念并不新鲜。|2542395|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

For me, a Service Oriented Architecture comes about when an Enterprise wishes to integrate a selection of disparate applications which concern a common domain into a set of interoperable services which operate against a single data source.

In the case of a new startup company with an idea for an item of software/suite of softwares, I can't see how a company can kick off with a Service Oriented Architecture from the off. At first, each solution (which may well evolve into a service such that it may become interoperable) should seek to solve its problem space in isolation.

Perhaps it will be in the roadmap for an enterprise capability or suite for each solution to become an interoperable service as the solutions are completed and enter service. For this, perhaps the development teams will undertake a modular/component oriented approach to building the soluton (eventual service), so as to make it easier to include the solution as a service in a Service Oriented Architecture.

In the case where existing islands of software are to become interoperable services in a Service Oriented Architecture, the approach allows for the software items - which may be distributed and may be written in different languages - to communicate via an exposed API and/or common protocol (for example a flavor of Web Service) and generic data format (for example XML).

SOA is an approach or idea. It is not a framework or a tool. When WDSLs and EJBs get name-dropped, this is often forgotten... as is that the idea of SOA is not new at all.

blocks|key|55145|text|这里的大多数答案似乎传达了SOA+(Service+Oriented+architecture)是关于以标准化的方式构建应用程序，以便其他应用程序可以以独立于平台的方式与其交互。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|55146|我不确定自那以后含义是否改变了，但我有机会与一家提供SOA套件的公司合作，以下是我对此的看法。|55147|当然，当你设计一个应用程序时，你不能保证它是跨平台兼容的。以stock+Trading+systems为例。它们使用Fix+protocol来传输消息。您希望它现在以XML格式返回数据，以便可以所谓的SOA兼容吗？绝对不是那么回事!SOA是一种架构方法，可以帮助您decouple+your+application/services并让它们彼此交互。面向服务架构的主干是用来将数据从一个服务传输到另一个服务的ESB+(Enterprise+Service+Bus)。SOA架构应该负责格式转换。例如：|55148|FIX(Service+1)+->+(XML+---ESB--->+XML)+->+JSON+(Service+2)|code-block|syntax|javascript|55149|这些转换模块通常被称为adapters，并且通常是SOA套件的一部分。有关更多信息，请参考另一个答案-|55150|Difference+between+SOA+and+ESB|55151|当然，SOA是一个为了营销目的而大肆宣传的词。从技术上讲，它就像反序列化和序列化数据一样简单，这样服务就可以解耦并独立于平台，但它背后的想法是具体的。|55152|也可以参考Wiki+page获取相同的信息。|55153|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/14872020/difference-between-soa-and-esb/28127649#28127649|1|http://en.wikipedia.org/wiki/Service-oriented_architecture^0|D|Z|0|0|U|L|1M|C|3O|Y|5O|S|0|0|B|8|0|0|U|0|0|0|5|9|1|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1J|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1N|8|@]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|S|3|T|5|6|7|1R|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1S|8|@]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|W|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]|14|$5|Z|10|11|E|$12|15]]]]

Most of the answers here seems to convey that <code>SOA (Service Oriented architecture)</code> is about building application in a standardized manner so that other applications can interact with it in platform independent manner. 

I am not sure if meaning has changed since but I have had an opportunity to work with a company that offers SOA suite and following are my thoughts on it.

Of course when you design an application you cannot guarantee it will be cross platform compliant. Take for example <code>stock Trading systems</code>. They use <code>Fix protocol</code> to transfer messages. Do you expect it now to return data in XML format so that it can be so called SOA compliant? Definitely not! SOA is an architectural approach that can help you <code>decouple your application/services</code> and let them interact with each other. Backbone of SOA is a <code>ESB (Enterprise Service Bus)</code> which is used to transfer data from one service to other. SOA architecture should take care of formats conversions. For example -

<pre><code>FIX(Service 1) -&gt; (XML ---ESB---&gt; XML) -&gt; JSON (Service 2)
</code></pre>

These conversion modules are commonly called as <code>adapters</code> and are generally part of SOA suite. For a bit more information refer to another answer - 

<a href="https://stackoverflow.com/questions/14872020/difference-between-soa-and-esb/28127649#28127649">Difference between SOA and ESB</a>

Sure SOA is a word is hyped for marketing purpose. Technically speaking it as simple as de-serializing and serializing data so that services can be decoupled and platform independent but the idea behind it is concrete.

Also refer <a href="http://en.wikipedia.org/wiki/Service-oriented_architecture" rel="nofollow noreferrer">Wiki page</a> for the same.

blocks|key|55178|text|面向服务的体系结构()是一种体系结构模式，其中软件被设计为构建块。即模块化开发，这使得我们可以灵活地以任何我们想要的方式进行组装。如果你想开始新的项目而不是从头开始，我们可以重用服务，如果你想要新的服务，我们可以很容易地集成现有的服务来创建新的项目。因此，我们可以节省大量的时间，并且money.The面向服务架构的基本原则独立于供应商、产品和技术。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|55179|类比:使用乐高积木构建玩具。|55180|​|55181|📷|atomic|55182|55183|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5035d511294cdba55a3bd0ff08508284.jpeg|imageAlt^0|A|1|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|M|3|I|5|6|7|15|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U|V|-4]]]]

A service-oriented architecture (SOA) is an architectural pattern in which softwares are designed as building block. i.e. Modular development, which makes flexibility to assemble any way we want. If you want to start new project instead of starting from scratch, we can reuse the services and if you want to new service we can easily integrate with existing service to make new project. So we can save lot of time and money.The basic principles of service oriented architecture are independent of vendors, products and technologies. 

Analogy: Toys build using Lego building blocks.

<a href="https://i.stack.imgur.com/CLVuz.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CLVuz.jpg" alt="Lego toys build using Lego bricks"></a>

blocks|key|56145|text|实际上，SOA是定义良好的服务的集合。基本上，SOA使用松散耦合的服务来轻松地获得期望的结果。服务的实现细节对客户端/使用者是隐藏的，因此实现中的任何更改都不会影响服务，直到它们之间的契约发生更改。服务提供者是基于预先确定的输入和输出执行某些业务逻辑的组件，并通过SOA实现公开此功能。这使得基于SOA的系统能够更快、更经济地为业务做出响应。组件和SOA之间的主要区别在于，SOA提供了一种开放的标准消息，该消息并不特定于任何编程语言或平台。因此，您可以实现跨平台和技术的高度松散耦合和互操作性。在传统的客户机-服务器世界中，提供者将是服务器，使用者将是client.You可以在这里阅读更多关于SOA的内容:Service+Oriented+architecture+(SOA)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|56146|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mssql-dotnetservices.com/2016/09/service-oriented-architecture-soa.html^0|8H|Z|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

In reality, SOA is a collection of well-defined services. Basically SOA use loosely coupled service to get the desire result easily. Implementation details of a service are hidden from the client/consumer so any change in the implementation doesn’t affect the service until the contract between them is change. Service providers are components that execute some business logic based on predetermined inputs and outputs, and expose this functionality through an SOA implementation. This allows systems based on SOA to respond more quickly and cost effectively for the business. The main difference between component and SOA is that, SOA provide a open standards message which is not specific to any programming language or platform. As a result, you can achieve a high degree of loose coupling and interoperability across platforms and technologies. In a traditional client-server world, the provider will be a server and the consumer will be a client.You can read more about SOA here :<a href="http://www.mssql-dotnetservices.com/2016/09/service-oriented-architecture-soa.html" rel="nofollow">Service Oriented architecture (SOA)</a>

blocks|key|55783|text|事实上，SOA还利用了client-servier架构。此外，SOA是一种设计软件的方法。假设您的应用程序可以分解为简单而独立的任务，如搜索图书、添加新书、根据用户偏好推荐图书等。如果您考虑为每个任务使用一个服务(+API)，那么实际上您正在使用SOA。此架构的优势在于，无论您是构建web应用程序还是移动应用程序，您只需要开发上述服务(API)即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|55784|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In fact, SOA also utilizes client-servier architecture. In addition, SOA is a way to design your software. Suppose that your application can break into simple and independent tasks like search a book, add new book, recommend a book according to user preference and so forth. If you consider a service (an API) for each of task, actually, you are using SOA. The advantage of this architecture is doesn't matter you're building a web app or mobile app, you only need the developed aforementioned services (APIs).

blocks|key|56158|text|面向服务的体系结构(+Service-oriented+architecture，SOA)是一种设计方法，其中多个服务协作以提供某些最终的功能集。这里的服务通常意味着一个完全独立的操作系统进程。这些服务之间的通信是通过网络调用进行的，而不是通过进程边界内的方法调用进行的。SOA的出现是为了应对大型单片应用程序的挑战。这是一种旨在提高软件可重用性的方法；例如，两个或多个最终用户应用程序都可以使用相同的服务。它的目的是让维护或重写软件变得更容易，因为理论上我们可以在没有人知道的情况下用一个服务替换另一个服务，只要服务的语义不会发生太多变化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|56159|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Service-oriented architecture (SOA) is a design approach where multiple services
collaborate to provide some end set of capabilities. A service here typically means a
completely separate operating system process. Communication between these services
occurs via calls across a network rather than method calls within a process boundary.
SOA emerged as an approach to combat the challenges of the large monolithic
applications. It is an approach that aims to promote the reusability of software; two or
more end-user applications, for example, could both use the same services. It aims to
make it easier to maintain or rewrite software, as theoretically we can replace one service
with another without anyone knowing, as long as the semantics of the service don’t
change too much.

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, my 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. 

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?

What is SOA (Service Oriented Architecture)?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

如果你愿意，可以称我为巨魔，但我是认真的：新的面向服务架构趋势与我15年前构建的客户端服务体系结构到底有什么不同？我不断听到面向服务的体系结构，但我看不出它与我们一直所做的有什么不同。回到10年前，我的公司有多个客户(使用多种语言)与相同的服务对话。它不是XML (它是一种称为Microsoft DCOM的二进制协议)...

问什么是SOA (面向服务的体系结构)？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是SOA (面向服务的体系结构)？EN