blocks|key|2821708|text|它也可以代表“数组结构”(相对于“Structs阵列”)，这是并行(特别是SIMD)编程中的一个常见主题，但我猜这不是您的意思！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2821709|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|$]]

It could also stand for "Struct of Arrays" (as opposed to "Array of Structs") which is a common topic in parallel (especially SIMD) programming, but I'm guessing that's not what you mean here!

blocks|key|1179128|text|您可能会发现本文(什么是SOA？-+SOA和Web服务解释)很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1179129|一个小小的挑逗：|1179130|SOA是一种架构应用程序的方式，它们由具有简单、定义良好的接口的离散软件代理组成，并通过松散耦合来执行所需的功能。|unordered-list-item|1179131|SOA中有两个角色--服务提供者和服务使用者。软件代理可以同时扮演这两种角色。SOA并不是一个全新的概念--然而，本文主要关注的是用web服务实现的SOA。|1179132|entityMap|0|LINK|mutability|MUTABLE|url|http://www.indiawebdevelopers.com/resource_center/articles/soa.html^0|6|O|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$]]|$1|I|3|J|5|H|7|Y|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

You might find <a href="http://www.indiawebdevelopers.com/resource_center/articles/soa.html" rel="noreferrer">this article (What is SOA? - SOA and Web Services Explained )</a> helpful.

A little teaser:

<ul>
<li>SOA is a style of architecting applications in such a way that they are composed of discrete software agents that have simple, well defined interfaces and are orchestrated through a loose coupling to perform a required function.</li>
<li>There are 2 roles in SOA- a service provider and a service consumer. A software agent may play both roles. SOA is not an entirely new concept – however, this article mainly focuses on SOA as implemented with web services.</li>
</ul>

blocks|key|1298611|text|据我所知，基本概念是创建小的“服务”，为其他系统提供有用的东西，并避免构建大系统来完成系统内的一切。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1298612|因此，您定义了一个用于交互的协议(例如，它可能是SOAP服务)，并让您的“系统-做一些业务-工作”与小型服务交互，以实现您的“大目标”。|1298613|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

As far as I understand, the basic concept there is that you create small "services" that provide something useful to other systems and avoid building large systems that tend to do everything inside the system. 

So you define a protocol which you will use for interaction (say, it might be SOAP web services) and let your "system-that-does-some-business-work" to interact with the small services to achieve your "big goal".

blocks|key|1178268|text|听一听本周的牙线周刊播客，它涵盖了SOA。这些描述是很高层次的，不要钻研太多的技术细节(尽管SOA项目更具体、更容易识别的例子可能会有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1178269|entityMap|0|LINK|mutability|MUTABLE|url|http://twit.tv/floss103^0|6|4|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]]]]

Have a listen to this week's edition of the <a href="http://twit.tv/floss103" rel="nofollow noreferrer">Floss Weekly</a> podcast, which covers SOA. The descriptions are pretty high level and don't delve into too many technical details (although more concrete and recognizable examples of SOA projects would have been helpful.

blocks|key|2821850|text|传统的应用程序体系结构是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2821851|用户界面|unordered-list-item|2821852|封装/隐藏在用户界面后面的未定义的东西(实现)|2821853|如果要以编程方式访问数据，则可能需要使用屏幕抓取。|2821854|在我看来，SOA似乎是一种专注于公开机器可读数据和/或API的体系结构，而不是公开UI。|2821855|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

A traditional application architecture is:

<ul>
<li>A user interface</li>
<li>Undefined stuff (implementation) that's encapsulated/hidden behind the user interface</li>
</ul>

If you want to access the data programmatically, you might need to resort to screen-scraping.

SOA seems to me to be an architecture which focus on exposing machine-readable data and/or APIs, instead of on exposing UIs.

blocks|key|1179193|text|SOA是面向服务体系结构的缩写。。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1179194|SOA正在设计和编写软件应用程序，使不同的软件模块能够以高度的可重用性无缝集成。
大多数人将SOA限制为编写客户机/服务器软件-web服务。但是SOA的上下文太小了。SOA的规模要大得多，在过去几年中，web服务一直是通信的主要媒介，这可能是人们将SOA看作web服务的原因，通常限制SOA的边界和意义。|blockquote|1179195|您可以考虑编写一个数据库访问模块，该模块非常独立，可以在没有任何依赖关系的情况下独立工作。该模块可以公开任何需要数据库访问的主机软件都可以使用的类.在主机应用程序中没有启动配置。所需或所需的内容都是通过由数据库访问模块公开的类进行交流的。我们可以将这些类作为服务调用，并将模块视为启用服务的模块。|1179196|实践SOA提供了高度的可重用性，通过强制DRY+--不要重复您自己，这将导致高度可维护的软件。可维护性是任何软件架构想到的第一件事--+SOA给了您这样的机会。|1179197|entityMap^0|0|G|0|0|14|15|33|0|0|44|0|0|28|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|I|3|J|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|K|3|L|5|H|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$]]

SOA is acronym for Service Oriented Architecture.

<blockquote>
 SOA is designing and writing software applications in such a way
 that distinct software modules can be
 integrated seamlessly with high degree
 of re-usability. 
 
 Most of the people
 restrict SOA as writing client/server
 software-web-services. But it is too
 small context of SOA. SOA is much
 larger than that and over the past few
 years web-services have been primary
 medium of communcation which is
 probably the reason why people think
 of SOA as web-services in general
 restricting the boundaries and meaning
 of SOA.
</blockquote>

You can think of writing a database-access module which is so independent that it can work on its own without any dependencies. This module can expose classes which can be used by any host-software that needs database access. There's no start-up configuration in host-application. Whatever is needed or required is communicated through classes exposes by database-access module. We can call these classes as services and consider the module as service-enabled.

<blockquote>
 Practicing SOA gives high degree of
 re-usability by enforcing DRY [Don't
 repeat your self] which results into
 highly maintainable software.
 Maintainability is the first thing any
 software architecture thinks of - SOA
 gives you that.
</blockquote>

blocks|key|1298718|text|SOA是一种体系结构风格，但也是关于如何开发和集成异构应用程序的远景。SOA的主要目的是摆脱单块应用程序()，而拥有一组可重用的服务，这些服务可以用来构建应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1298719|IMHO，SOA只在企业级有意义，对于单个应用程序来说没有任何意义。|1298720|在许多企业中，每个部门都有自己的一组企业应用程序，这意味着|1298721|类似的特性已多次实现。|ordered-list-item|1298722|数据(例如客户或员工数据)需要在多个应用程序之间共享。|1298723|申请是以部门为中心的。|1298724|有了SOA，我们的想法是让可重用的服务在企业范围内可用，这样应用程序就可以由它们构建和组合。SOA的承诺是|1298725|无需一次又一次地重新实现类似的功能(例如提供客户或员工服务)|1298726|有助于将应用程序集成在一起，并便于访问公共数据或特性。|1298727|以企业为中心的发展努力。|1298728|SOA愿景需要一个technological转换以及一个organizational转换。虽然它解决了一些问题，但它也引入了其他一些问题，例如，与单块应用程序相比，SOA的安全性要难得多。因此，SOA是否工作是讨论的焦点。|1298729|这是SOA的1000英尺视图。然而，它并不止于此。对SOA进行补充的概念还有业务流程编排(BPM)、企业服务总线(ESB)、复杂事件处理(CEP)等，它们都解决了+IT+/业务对齐的问题，即如何使IT能够有效地支持业务。|1298730|entityMap^0|W|2|1A|7|1S|2|0|0|0|0|0|0|0|0|0|0|9|D|S|E|0|29|9|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1B|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1C|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1D|8|@]|D|@]|E|$]]|$1|M|3|N|5|L|7|1E|8|@]|D|@]|E|$]]|$1|O|3|P|5|L|7|1F|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1G|8|@]|D|@]|E|$]]|$1|S|3|T|5|L|7|1H|8|@]|D|@]|E|$]]|$1|U|3|V|5|L|7|1I|8|@]|D|@]|E|$]]|$1|W|3|X|5|L|7|1J|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|10|3|11|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|12|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|13|$]]

SOA is an architectural style but also a vision on how heterogeneous application should be developped and integrated. The main purpose of SOA is to shift away from monolithic applications and have instead a set of reusable services that can be composed to build applications. 

IMHO, SOA makes sense only at the enterprise-level, and means nothing for a single application. 

In many enterprise, each department had its own set of enterprise applications which implied 

<ol>
<li>Similar feature were implemented several times</li>
<li>Data (e.g. customer or employee data) need to be shared between
several applications</li>
<li>Applications were department-centric.</li>
</ol>

With SOA, the idea is to have reusable services be made available enterprise-wide, so that application can be built and composed out of them. The promise of SOA are 

<ol>
<li>No need to reimplement similar features over and over (e.g.
provide a customer or employee service)</li>
<li>Facilitates integration of applications together and the access
to common data or features </li>
<li>Enterprise-centric development
 effort.</li>
</ol>

The SOA vision requires an technological shift as well as an organizational shift. Whereas it solves some problem, it also introduces other, for instance security is much harder with SOA that with monolithic application. Therefore SOA is subject to discussion on whether it works or not.

This is the 1000ft view of SOA. It however doesn't stop here. There are other concepts complementing SOA such as business process orchestration (BPM), enterprise service bus (ESB), complex event processing (CEP), etc. They all tackle the problem of IT/business alignement, that is, how to have the IT be able to support the business effectively.

blocks|key|1298779|text|你看..。SOA代表面向服务的体系结构..。最简单的说法是，您编写了一段非常通用的代码，即它做了一些可以用于许多应用程序的事情.可能是类似地址簿的东西，也可能是计算器。然后在IIS上启动这段代码。因此，您可以通过代码提供服务。所以你是一个服务提供者。现在有人想要使用类似的代码，那么他就不必再编写代码了。他只是简单地使用你的代码，也许是通过一个web服务。因此，他成为了服务消费者。因此，使用此类服务制作程序称为SOA。由于服务提供者和使用者可能正在交互，即使他们使用的是diff编程语言，松耦合也是存在的。希望你能理解。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1298780|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|$]]

Well You see.. SOA stands for Service Oriented Architecture.... In simplest words, you write a piece of code that is very generic i.e. it does some thing that can be used in a lot of applications ... may be something like a address book or may be a calculator. and you launch this code on the IIS. So you provide a service through your code. So you are a service provider. Now someone wants to use a similar code then he does not have to write the code again. He simply uses your code maybe through a web service. Hence he becomes a service consumer. Hence making a program using such services is called SOA. And the loose coupling is there as the service provider and consumer may be interacting even if they are using diff programming languages.
Hope you understand.

blocks|key|1298832|text|SOA是一些非常古老的想法的新徽章：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1298833|将代码划分为可重用模块。|unordered-list-item|1298834|将可能更改的任何设计决策封装在模块中。|1298835|设计您的模块时，可以将它们以不同的有用方式组合(有时被称为“家庭”或“产品线”)。|1298836|这些都是基本的软件开发原则，其中许多是由David首先阐述的。|1298837|SOA中的新内容是|1298838|你是在网络上做的。|1298839|模块之间通过网络相互发送消息进行通信，而不是使用更传统的编程机制(如过程调用)。特别是，在面向服务的体系结构中，部分通常不共享可变状态(传统程序中的全局变量)。或者，如果它们确实共享状态，则将该状态小心地锁定在数据库中，该数据库本身就是一个代理，可以轻松地管理多个并发客户端。|1298840|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|U|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|X|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Y|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Z|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|R|$]]

SOA is a new badge for some very old ideas:

<ul>
<li>Divide your code into reusable modules.</li>
<li>Encapsulate in a module any design decision that is likely to change.</li>
<li>Design your modules in such a way that they can be combined in different useful ways (sometimes called a "family" or "product line").</li>
</ul>

These are all bedrock software-development principles, many of them first articulated by David Parnas.

What's new in SOA is

<ul>
<li>You're doing it on a network.</li>
<li>Modules are communicating by sending messages to each other over the network, rather than by more tradtional programming-language mechanisms like procedure calls. In particular, in a service-oriented architecture the parts generally don't share mutable state (global variables in a traditional program). Or if they do share state, that state is carefully locked up in a database which is itself an agent and which can easily manage multiple concurrent clients.</li>
</ul>

blocks|key|1298905|text|假设你有四个厨师。在SOA中，您假设他们彼此讨厌，所以您努力让他们尽可能少地交谈。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1298906|你怎么做到的？那么，你将首先定义角色和界面-厨师1将做沙拉，厨师2将做汤，厨师3将做牛排，等等。然后，你会把盘子摆放在桌子上(所以这些是界面)，然后说：“每个人都把你的创意放进你指定的盘子里。别在意其他人。”|1298907|这样，四位厨师必须尽可能少地交谈，这在软件开发方面非常好--不一定是因为他们彼此讨厌，而是出于其他原因，比如地理位置，决策的效率等等。|1298908|这也意味着你可以根据自己的喜好重新组合菜肴(服务)。例如，你可以用甜品来服务一家咖啡馆，或者把汤和你从另一家公司买来的面包结合起来，提供更便宜的菜单，或者让其他餐馆用你的沙拉和他们的菜肴搭配，等等。|1298909|SOA最成功的实现之一是在Amazon。由于他们的设计，他们可以重新包装他们的整个基础设施，并将其作为Amazon服务出售。|1298910|*这只是SOA的一个方面。|1298911|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Let's assume you have four cooks. In SOA, you assume they hate each other, so you strive to let them have to talk to each other as little as possible.

How do you do that? Well, you will first define the roles and interface -- cook 1 will make salad, cook 2 will make soup, cook 3 will make the steak, etc.. Then you will place the dishes well organised on the table (so these are the interfaces) and say, "Everybody please place your creation into your assigned dishes. Don't care about anybody else.".

This way, the four cooks have to talk to each other as little as possible, which is very good in software development -- not necessarily because they hate each other, but for other reasons like physical location, efficiency in making decisions etc. 

It also means you can recombine the dishes (services) as you like. For example, you might just use the dessert to service a cafe, or just take the soup and combine it with a bread you bought from another company to provide a cheaper menu, or let other restaurants use your salads to combine with their dishes, etc.

One of the most successful implementation of SOA was at Amazon. Because of their design, they could re-package their whole infrastructure and sell it as Amazon Web Service. 

*This is only one aspect of SOA.

blocks|key|1298924|text|从它的工具箱博客。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1298925|以下概述了过去设计技术的相似之处和不同点：|1298926|·SOA与结构化编程的相似之处:最类似于传递参数的子例程调用，函数的操作是从调用方抽象出来的，例如CICS链接和执行以及COBOL调用保留字。复制簿用于定义数据结构，数据结构通常定义为服务的XML架构。O差异:+SOA是松散耦合的，意味着对服务的更改对使用者(“调用”程序)的影响较小，而且服务可以跨语言和跨平台互操作。|1298927|·SOA与OOA/OOD+o相似之处:封装、抽象和定义接口o的差异:+SOA是松散耦合的，没有类层次结构或继承、低级抽象类级别与业务服务。|1298928|·SOA与基于遗留组件的开发(CBD)+--例如CORBA、DCOM、EJB+o相似性:通过组装组件重用、接口、远程调用o差异:广泛采用标准、XML模式与封送对象、服务编排、重用设计更容易、服务专注于业务而不是以IT为中心、业务服务是过程粒度的(范围很广)|1298929|·SOA+(用于集成)与企业应用程序集成(EAI)的相似之处:最佳实践(定义良好的接口、标准化的模式、事件驱动的体系结构)、可重用的接口、公共模式和差异:标准、采用和改进的工具|1298930|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

from ittoolbox blogs.

The following outlines the similarities and differences to past design techniques:

• SOA versus Structured Programming 
o Similarities: Most similar to subroutine calls where parameters are passed and the operation of the function is abstracted from the caller - e.g. CICS link and execute and the COBOL CALL reserved word. Copybooks are used to define data structure which is typically defined as an XML schema for services. 
o Differences: SOA is loosely coupled implying changes to a service have less impact to the consumer (the "calling" program) and services are interoperable across languages and platforms. 

• SOA versus OOA/OOD 
o Similarities: Encapsulation, Abstraction and Defined Interfaces 
o Differences: SOA is loosely coupled with no class hierarchy or inheritance, Low-level abstractions - class level versus business service 

• SOA versus legacy Component Based Development (CBD) - e.g. CORBA, DCOM, EJB
o Similarities: Reuse through assembling components, Interfaces, Remote calls 
o Differences: Wide adoption of standards, XML Schemas vs. Marshaled Objects, Service Orchestration, Designing for reuse is easier, services are business focused vs. IT focused, business services are course grained (broad in scope) 

• SOA (for integration) versus Enterprise Application Integration (EAI) 
o Similarities: Best practices (well defined interfaces, standardized schemas, event driven architecture), reusable interfaces, common schemas 
o Differences: Standards, adoption, and improved tools

blocks|key|1179320|text|读到上面的回答，我觉得SOA是开发者(至少是优秀的)从第一天起就一直在做的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1179321|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|$]]

Reading the responses above, it sounds to me that SOA is what developers (good ones at least) have been doing from day one.

blocks|key|1299039|text|在大型组织中往往会发生的是，随着时间的推移，任何事情都是单一的或完全不同的系统，或者两者兼而有之。最后有人进来说我们搞砸了。现在，你想要重新设计(钱给某人)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1299040|因此，您可以购买Oracle的SOA，而Oracle将成为您所有部件的老大。所有其他参与者都必须通过服务(web服务或其他任何东西)使用SOA。甲骨文负责一切事务(monolith并不意味着贬义)。哦，是的，你把ASP.NET+MVC放在前面或者别的什么地方。|1299041|主要的事情是在不受影响的情况下将东西移进或移出它们的系统，并且保持供应商Oracle+SOA，Microsoft作为所有这些系统的大脑。所有的东西都是流动的、流动的、几乎没有影响的东西，甚至是人类服务，而不仅仅是电脑。|1299042|对我来说，它仅仅意味着一堆有着良好前端的web服务(或者将来我们称之为它们的任何服务)。如果你拥有数据库，就点击数据库，不要再担心流行词汇了。没关系的。|1299043|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

what tends to happen in large organizations is that over time everything is either monolithic or disparate systems everywhere or a little of both. Someone eventually comes in and says we've got a mess. Now, you want to re-design (money to someone) everything to be oriented in a sort of monotlithic depends on who you pay paradigm but at the same time be able to add pieces and parts independently of the master/monolith.

So you buy Oracle's SOA and Oracle becomes the boss of all your parts. All the other players coming in have to work with SOA via a service (web service or whatever it has.) The Oracle monolith takes care of everything (monolith is not meant derogatory). Oh yeah, you got ASP.NET MVC on the front or something else.

main thing is moving things in and out of they system without impact and keeping the vendor Oracle SOA, Microsoft WCF, as the brains of it all. everything's all oop/ood like, fluid, things moving in and out with little to no impact, even human services, not just computers.

To me it just means a bunch of web services (or whatever we call them in the future) with a good front end. And if you own the database just hit the database and stop worrying about buzzwords. it's okay.

blocks|key|2822249|text|只有一项建议：-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2822250|请阅读托马斯·厄尔(+Thomas+)的“SOA概念、技术与设计”。|offset|length|2822251|它用简单的英语和案例研究给出了关于SOA的详细信息。|2822252|entityMap|0|LINK|mutability|MUTABLE|url|http://soabooks.com/ctd/^0|0|L|B|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Only one suggestion:-

Read <a href="http://soabooks.com/ctd/" rel="nofollow">SOA Concepts, Technology and Design</a> by Thomas Erl. 

It has very beautifully given the details about SOA in plain English and with case studies.

blocks|key|1179437|text|我建议您阅读Thomas和Roger的文章，这将使您对SOA的所有内容有一个明确的了解。这些也是很好的资源，看看为老板解释的SOA，一个是外行的解释。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1179438|构建SOA|offset|length|1179439|SOA设计模式|1179440|在SOA中实现完整性|1179441|为什么你的SOA应该像大众甲壳虫|1179442|为你的老板解释SOA|1179443|WCF服务性能|1179444|entityMap|0|LINK|mutability|MUTABLE|url|http://hubpages.com/_1k9ore6as3b3m/hub/Building-Service-Orientated-Architecture|1|http://hubpages.com/_1k9ore6as3b3m/hub/SOA-Design-Pattern-WCF|2|http://hubpages.com/_1k9ore6as3b3m/hub/Achieving-Non-Functional-Requirements-for-a-Service-Oriented-Software-Platform-Integrity|3|http://hubpages.com/_1k9ore6as3b3m/hub/Why-your-Service-Orientated-Architecture-SOA-needs-to-be-like-a-VW-Beetle|4|http://hubpages.com/_1k9ore6as3b3m/hub/soa-with-wcf|5|http://hubpages.com/_1k9ore6as3b3m/hub/WCF-Service-Performance^0|0|0|5|0|0|0|7|1|0|0|A|2|0|0|G|3|0|0|A|4|0|0|7|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]]]]

I would suggest you read articles by Thomas Erl and Roger Sessions, this will give you a firm handle on what SOA is all about. These are also good resources, look at the SOA explained for your boss one for a layman explanation

<a href="http://hubpages.com/_1k9ore6as3b3m/hub/Building-Service-Orientated-Architecture" rel="noreferrer">Building a SOA</a>

<a href="http://hubpages.com/_1k9ore6as3b3m/hub/SOA-Design-Pattern-WCF" rel="noreferrer">SOA Design Pattern</a>

<a href="http://hubpages.com/_1k9ore6as3b3m/hub/Achieving-Non-Functional-Requirements-for-a-Service-Oriented-Software-Platform-Integrity" rel="noreferrer">Achieving integrity in a SOA</a>

<a href="http://hubpages.com/_1k9ore6as3b3m/hub/Why-your-Service-Orientated-Architecture-SOA-needs-to-be-like-a-VW-Beetle" rel="noreferrer">Why your SOA should be like a VW Beetle</a>

<a href="http://hubpages.com/_1k9ore6as3b3m/hub/soa-with-wcf" rel="noreferrer">SOA explained for your boss</a>

<a href="http://hubpages.com/_1k9ore6as3b3m/hub/WCF-Service-Performance" rel="noreferrer">WCF Service Performance</a>

blocks|key|1299227|text|我看到了许多解释面向服务体系结构(，SOA)的答案，它们使用了更高级的词汇和技术术语。我想试着用通俗易懂的英语比喻，给外行解释一下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1299228|，但首先是对SOA的描述|offset|length|style|BOLD|1299229|SOA可以用三个层来描述，如下图所示。一方面我们有提供者，另一方面我们有消费者，两者之间有一个沟通桥梁。|1299230|使用者使用其业务所需的许多应用程序，而提供者使用为这些应用程序提供信息的组件。他们通过一组使用公共架构的服务进行通信。|1299231|​|1299232|📷|atomic|1299233|1299234|类推|1299235|想象一下乡村一侧的一栋房子，它在很多方面都是一个更大的社区的一部分，就像一个城市或城镇。这个城市有自己的复杂系统来提供水和电力，处理卫生设施，提供交通和其他公用事业。在这种模式中，房子是消费者，城市(或社区)是提供者，管道、下水道、电力线、光纤等是它们通信的基础设施。|1299236|这个模型可以松散地与SOA进行比较。房子里的人使用许多不同的“应用程序”，比如散热器、电脑、厕所、灯具、地板暖气、浴缸等等。这些应用程序不关心城市如何产生水、产生电力或处理废物，只要它正常工作。城市的组成部分是发电机、水泵和环卫区。它为房子提供了所有这些需求，但这取决于房子以它认为合适的方式使用。|1299237|我希望这至少给了某人一个更好的SOA图片。|1299238|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/4e4657255cccc254630fd3e8648a960d.jpg|imageAlt^0|0|0|9|0|0|0|0|0|1|0|0|0|0|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1E|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1F|8|@]|9|@$D|1G|E|1H|1|1I]]|A|$]]|$1|Q|3|M|5|6|7|1J|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1K|8|@$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1N|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1O|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16|17|-4]]]]

I see many answers explaining a Service Oriented Architecture (SOA) using even more advanced words and technical terms. I'd like to give a shot at explaining it for the layman, using an analogy in plain english. 

But first a description of a SOA 
SOA could be described in three layers as seen in the picture below. On one side we have the Provider and on the other side we have the Consumer, separated by a Bridge where the two sides communicate. 

The consumer uses a number of Applications necessary for it's business and the provider uses Components that provide these applications with information. They communicate through a set of Services using a common architecture. 

<hr/>
<img src="https://i.stack.imgur.com/oPYbg.jpg" alt="enter image description here">

<hr/>

The analogy 
Imagine a house on the country side, that in many ways is part of a larger community, like a city or town. The city has it's own complex systems for providing water and electricity, handling sanitation, providing transportation and other utilities. The House is the consumer in this model, the City (or community) is the provider and the pipes, sewers, powerlines, optical fibers etc. is the Infrastructure in which they communicate. 

This model could loosely be compared to a SOA. The people in the house uses a number of different "applications" like radiators, computers, toilets, lamps, underfloor heating, bathtubs etc. These applications don't care how the city generates the water, creates the electricity or handles the waste as long as it works. The components of the city are generators, water pumps and sanitation areas. It provides the house with all these needs but it's up to the house to use it in what ever way it sees fit. 

I hope this gave at least someone a better picture of a SOA.

blocks|key|2822462|text|SOA或面向服务的体系结构是一种软件体系结构模式，在这种模式中，应用程序或系统是从底层(通常是分布式的)软件服务构建的，这些服务符合特定的一组特征，即：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2822463|基于接口、策略和合同的|ordered-list-item|2822464|位置透明性|2822465|自治|2822466|摘要|2822467|可重复使用|2822468|可合成|2822469|无国籍|2822470|可发现|2822471|可扩展|2822472|松耦合|2822473|SOA的主要目标是软件开发的敏捷性，即能够轻松、廉价地响应更改，从而允许企业快速响应不断变化的市场。|2822474|服务通常(但绝不是唯一的)实现为web服务，即它们通过无处不在的web+HTTP协议进行操作，并且使用基于XML的SOAP或轻量级(更流行的)+REST范例来实现。|2822475|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|14|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|19|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1A|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1B|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1C|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1E|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|11|$]]

SOA or Service-Oriented Architecture is a software architecture pattern in which applications or systems are constructed from underlying (and usually distributed) software services that conform to a specific set of characteristics, namely:

<ol>
<li>Interface, Policy and Contract based</li>
<li>Location transparency</li>
<li>Autonomous</li>
<li>Abstract</li>
<li>Reusable</li>
<li>Composable</li>
<li>Stateless</li>
<li>Discoverable</li>
<li>Extensible</li>
<li>Loosely coupled</li>
</ol>

The primary goal of SOA is sofware development agility, i.e. the ability to respond the change easily, and cheaply, thus allowing businesses to rapidly respond to changing markets.

Services are typically (but by no means exclusively) implemented as web services, i.e. they operate over the ubiquitous web HTTP protocol, and are implemented either using XML-based SOAP or the lightweight (and more popular) REST paradigm.

blocks|key|1179546|text|SOA是技术供应商为帮助销售与企业服务总线(+Enterprise+)相关的技术而发明的一个热门词。这样做的目的是让企业中的小岛屿应用程序(例如:会计系统、库存控制系统等)都公开服务，以便将它们灵活地编排成“应用程序”，或者更确切地说，它们成为企业范围内的总体业务逻辑的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1179547|从根本上说，这是一堆几乎行不通的老掉牙的废话，因为它忽略了科技在企业中的地位，即科技之所以成为组织中的技术，其原因在于企业的文化、进化、历史，而企业的锁定程度如此之高，以至于任何重组技术的尝试都必然会失败。|1179548|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

SOA is a buzzword that was invented by technology vendors to help sell their Enterprise Service Bus related technologies. The idea is that you make your little island applications in the enterprise (eg: accounting system, stock control system, etc) all expose services, so that they can be orchestrated flexibly into 'applications', or rather become parts of aggregate enterprise scoped business logic.

Basically a load of old bollocks that nearly never works, because it misses the point that the reasons why technology is the way it is in an organisation is down to culture, evolution, history of the firm, and the lock in is so high that any attempt to restructure the technology is bound to fail.

blocks|key|1179556|text|取决于你是谁！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1179557|如果您是业务所有者，SOA是提高收入和业务敏捷性的解决方案。如果您是企业架构师，SOA是在空白画布上绘制漂亮而干净的软件的一种方法。如果您是架构师，SOA是在集成平台上设计松散耦合服务的解决方案，只需将服务插入插座即可。如果您是开发人员，SOA是一个编程范例，其中服务处于设计和代码的中心。|1179558|你应该读100-SOA-问题[pdf]|offset|length|1179559|干杯|1179560|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cin.ufpe.br/~redis/intranet/bibliography/services/100-SOA-Questions.pdf^0|0|0|4|F|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Depends on who you are! 

If you're an business owner, SOA is a solution to increase your incomes and business agility. If you're an entreprise architect, SOA is a way to draw nice and clean piece of software on a blank canvas. If you're an architect SOA is the solution to design loosely coupled services over an integration platform, to just plug services into outlets. If you're a developper SOA is a programming paradigm where a service is in the center of the design and the code.

You should read <a href="http://www.cin.ufpe.br/~redis/intranet/bibliography/services/100-SOA-Questions.pdf" rel="nofollow">100-SOA-Questions [pdf]</a>

Cheers

blocks|key|2822595|text|面向服务体系结构(，SOA)是一种软件体系结构风格，它将应用程序构建为可插接部件的集合，每个组件都可以被其他应用程序重用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2822596|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 software architectural style that builds applications as a collection of pluggable parts, each of which can be reused by other applications.

Can someone explain in plain english what is SOA all about? I hear SOA here, SOA there but I cannot understand exacly what it is and what is used for. Was it some simple concept and later evolved into something huge or what? 

All documents, including wiki are a bit abstract or maybe I'm an idiot and don't get it. Is there an idiot's guide on this? 

What exactly is there behind these three letters?

What is SOA "in plain english"?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

有人能用通俗易懂的来解释到底是什么吗？我在这里听说过SOA，但我无法确切地理解它是什么，以及它用于什么。这是一个简单的概念，后来演变成某种巨大的东西还是什么的？所有的文档，包括wiki都有点抽象，或者我是个白痴，不明白。这上面有白痴的向导吗？这三封信后面到底是什么？

问什么是SOA“在简单的英语”？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是SOA“在简单的英语”？EN