• SOA

  （面向服務的架構）

  編輯

面向服務的架構（SOA）是一個組件模型，它將應用程序的不同功能單元（稱為服務）通過這些服務之間定義良好的接口和契約聯系起來。接口是采用中立的方式進行定義的，它應該獨立於實現服務的硬件平臺、操作系統和編程語言。這使得構建在各種各樣的系統中的服務可以以一種統一和通用的方式進行交互。

A service-oriented architecture (SOA) is a style of software design where services are provided to the other components by application components, through a communication protocol over a network. The basic principles of service-oriented architecture are independent of vendors, products and technologies.^[1]

A service has four properties according to one of many definitions of SOA:^[2]

1. It logically represents a business activity with a specified outcome.

2. It is self-contained.

3. It is a black box for its consumers.

4. It may consist of other underlying services.^[3]

Different services can be used in conjunction to provide the functionality of a large software application.^[4] So far, the definition could be a definition of modular programming in the 1970s. Service-oriented architecture is less about how to modularize an application, and more about how to compose an application by integration of distributed, separately-maintained and deployed software components. It is enabled by technologies and standards that make it easier for components to communicate and cooperate over a network, especially an IP network.

https://en.wikipedia.org/wiki/Service-oriented_architecture

SOA面向服務架構

http://www.jdon.com/soa.html

SOA和微服務架構的區別？

https://www.zhihu.com/question/37808426

SOA架構設計經驗分享—架構、職責、數據一致性

• 1.背景介紹

• 2.SOA的架構層次

  • 2.1.應用服務（原子服務）

  • 2.2.組合服務

  • 2.3.業務服務（編排服務）

• 3.SOA化的重構

  • 3.1.保留服務空間，為了將來服務的組合

• 4.運用DDD+GRASP進行分析和設計（防止主觀的判斷導致錯誤的假設）

• 5.SOA分布式下的數據一致性

  • 5.1.分布式事務（基於DTC的分布式事務）

  • 5.2.事務補償（提供正向或反向的操作來讓數據在業務上是一致的）

  • 5.3.異步EDA（基於異步事件流來實現柔性的分布式事務）

• 6.總結

http://wangqingpei557.blog.51cto.com/1009349/1643999

本文出自 “運維自動化” 博客，請務必保留此出處http://shower.blog.51cto.com/4926872/1975965

SOA架構之學習路線