架构模式

架构模式是软件架构中在给定环境下常遇到问题的通用的、可重用的解决方案。[1]类似于软件设计模式但覆盖范围更广，致力于软件工程中不同问题，如计算机硬件性能限制、高可用性、业务风险极小化。[2][3]一些架构模式在软件框架被实现。

例子

子领域	架构模式	软件设计模式	解决方案模式	相关模式
数据集成/面向服务的架构(SOA)	提取转换加载(ETL)	变动数据捕获接近实时的ETL 批方式ETL 数据挖掘	异常处理作业调度器数据确认缓慢变化维度(SCD)	企业应用集成(EAI) 主数据hub 操作型数据存储 (ODS) 数据集市数据仓库
	受管文件传输(MFT)
	企业应用集成(EAI)/企业服务总线(ESB)	发布-订阅模式请求-响应方式消息传递模式	单行(One-way) 同步的请求-响应基本回调运单(Claim check)	面向服务的架构(SOA)
数据架构	在线交易处理 (TDS/OLTP) 主数据存储操作型数据存储 (ODS) 数据集市数据仓库	定制的应用数据库打包的应用数据库		ETL EAI SOA
分析与商业智能	业务报表(Transactional reporting) 运营分析商业分析预测分析指导性分析流式分析(Streaming analytics) 数据科学与高级分析自然语言处理(NLP)	业务报表数据访问运营分析数据访问分析报表数据访问分析dashboard数据访问运营dashboard数据访问数据挖掘	实时dashboards 在内存中分析(In-memory analytics) 统计分析预测分析	ETL EAI TDS 操作型数据存储 (ODS) 数据集市
主数据管理	主数据hub	主数据复制主数据服务主数据同步		变动数据捕获 EAI STD
数据建模	维度数据建模实体关系数据建模	建模标准命名惯例
人工智能	决策管理语音识别文本分析与自然语言处理自然语言生成传统机器学习深度学习机器人流程自动化图像与视频分析

一些额外的架构模式例子：

黑板 (设计模式)
Broker模式
事件驱动架构
隐式调用
分层 (面向对象设计)
微服务
模型-视图-控制器(MVC), 表示-抽象-控制, Model-view-presenter, 模型-视图-视图模型
实体-组件-系统
多层架构 (通常为3层或n层)
裸对象
操作型数据存储 (ODS)
点对点网络
管线与过滤器架构
面向服务的架构(SOA)
基于空间的架构

参见

软件架构风格与模式列表
过程驱动的消息服务
企业架构

参考文献

R. N. Taylor, N. Medvidović and E. M. Dashofy, Software architecture: Foundations, Theory and Practice. Wiley, 2009.
Chang, Chih-Hung; Lu, Chih-Wei; Lin, Chih-Hao; Yang, Ming-Feng; Tsai, Ching-Fu. . Journal of Software Engineering Studies, Vol. 2, No. 6. the Third Taiwan Conference on Software Engineering (TCSE07): 185–194. June 2008 [2012-05-16]. （原始内容存档于2011-09-22）. Furthermore, patterns are often defined as something "strictly described and commonly available". For example, layered architecture is a call-and-return style, when it defines an overall style to interact.
. AAHN INFOTECH (INDIA) PVT. LTD. [2012-05-16]. （原始内容存档于2012-06-23）. Even though an architectural pattern conveys an image of a system, it is not an architecture as such. An architectural pattern is rather a concept that solves and delineates some essential cohesive elements of a software architecture. Countless different architectures may implement the same pattern and thereby share the related characteristics. Furthermore, patterns are often defined as something "strictly described and commonly available".

书目

Avgeriou, Paris; Uwe Zdun. . 10th European Conference on Pattern Languages of Programs (EuroPlop 2005), Irsee, Germany, July. 2005.

Buschmann F.; Meunier R.; Rohnert H.; Sommerlad P.; Stal M. . John Wiley & Sons. 1996.

Bass L.; Clements P.; Kazman R. . Addison-Wesley. 2005.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.

[TMD-1] R. N. Taylor, N. Medvidović and E. M. Dashofy, Software architecture: Foundations, Theory and Practice. Wiley, 2009.

[2] Chang, Chih-Hung; Lu, Chih-Wei; Lin, Chih-Hao; Yang, Ming-Feng; Tsai, Ching-Fu. . Journal of Software Engineering Studies, Vol. 2, No. 6. the Third Taiwan Conference on Software Engineering (TCSE07): 185–194. June 2008 [2012-05-16]. （原始内容存档于2011-09-22）. Furthermore, patterns are often defined as something "strictly described and commonly available". For example, layered architecture is a call-and-return style, when it defines an overall style to interact.

[3] . AAHN INFOTECH (INDIA) PVT. LTD. [2012-05-16]. （原始内容存档于2012-06-23）. Even though an architectural pattern conveys an image of a system, it is not an architecture as such. An architectural pattern is rather a concept that solves and delineates some essential cohesive elements of a software architecture. Countless different architectures may implement the same pattern and thereby share the related characteristics. Furthermore, patterns are often defined as something "strictly described and commonly available".