重建N层应用到面向服务的架构（SOA）？ [英] Rebuild N-tier app into Service-Oriented Architecture (SOA)?

问题描述

考虑N层应用程序的常规特性与像层：presentation，业务，数据访问;这是怎么一般的重建，以使一个面向服务的架构（ SOA ）？

Considering the regular characteristics of an n-tier app with layers like: presentation, business, data access; how is this normally rebuilt to make a Service-Oriented Architecture (SOA)?

从程序员追求高层次的概述经历了此次演习。

Seeking high level overview from programmers experienced in this exercise.

在一定程度上我想象它在概念上不上不下的，而不是一个垂直堆栈。或作为一个系列卧式模块封装每一个自己的迷你n层堆栈。随着对消息之间较重的协议。

To a degree I picture it conceptually flattening out rather than having one vertical stack. Or as a series of horizontal modules each encapsulating their own mini n-tier stack. With heavier protocols in between for messaging.

推荐答案

SOA和n层是有些不同的概念。 n层通常为约构建一个独立的应用（其可具有一些定义的接口，以其他应用程序等等）的应用架构。

SOA and n-tier are somewhat different concepts. n-tier is generally about the application architecture of building a standalone application (which may have some defined interfaces to other applications etc).

从SOA这需要退后一步，看着所需整个企业，他们应该提供的地方，以目标减少重复的业务服务范围。这些很可能建立或重用现有的n层应用程序的元素。例如可能有一定数量的允许为了创建（例如Internet客户端基于通过销售团队的应用程序，网上网等）现有的应用程序，然后需要同步或在某些时候他们的汇总数据。代替'位置顺序服务可以创建，可以由许多不同的前端应用中重复使用。

SOA takes a step back from this and looks at the range of business services that are required across the enterprise and where they should be provided, with an aim to reduce duplication. These may well build on or reuse elements of existing n-tier applications. For example there might be a number of existing applications that allow an order to be created (e.g. intranet client based application by sales team, online at website etc), which then need to synchronise or aggregate their data at some point. Instead a 'place order' service could be created, that can be reused by a number of different front-end applications.

这些最初的服务很可能存在基于功能的现有应用程序是再包业务服务，以提供可重复使用的界面中。

These initial services could well exist based on functionality within existing applications that is then wrapped in a business service to provide the reusable interface.

然后，您可以看看以不同的方式（编排）链接多项服务一起提供组合服务 - 例如place_order后面是一个可选的呼叫到供应商公司的服务进货仓库，如果库存水平低于一定的水平，并进一步调用到账单服务提出创建发票等。

You might then look at chaining a number of services together in different ways (orchestration) to provide a composite service - e.g. place_order is followed by an optional call to a supplier company service to restock the warehouse if the stock level is below certain level, and a further call is made to a billing service to create an invoice etc.

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