关于SOA参考体系结构问题 [英] Questions about SOA reference architectures

查看:117
本文介绍了关于SOA参考体系结构问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有关于由开放组织为可用于为企业,例如SOA提供的参考架构一些混乱。

I have some confusion regarding the reference architecture provided by The Open Group for SOA that can be used as an example for enterprises.

问题1:在此参考架构有其暴露于外界一个服务的服务层。该标准文件说,你可以在此服务层,它实现一些功能的过程,可以作为服务被访问内有流程服务。它也可能有在服务层组成服务,利用其他服务。不过,也有它我的理解主要是从服务层编排不同的服务来实现业务流程的业务流程层。如何在业务流程层业务流程,从流程服务,在服务层有什么区别?

Question 1: Within this reference architecture there is the service layer which exposes a service to the outside world. The standards document says that you can have process services within this service layer, which implements some process of functionality that can be accessed as a service. It is also possible to have composed services in the service layer which make use of other services. However, there is also a Business Process layer which as I understand is mainly to implement a business process by orchestrating different services from the service layer. How do business processes in the Business Process layer differ from process services in the service layer?

问题2:是否有任何参数来决定你是否应该提供一个组成服务,使利用多种不同的服务:
1.通过给组合服务自身的接口,而在服务层中使用其他服务的服务层?
2.在业务流程层的业务内容的过程
3.在消费层处理它。

Question 2: Is there any argument to decide whether you should provide a composed service that makes use of multiple different services: 1. In the service layer by giving the composed service its own interface while using other services within the service layer? 2. As a busines process in the Business Process layer 3. by handling it in the consumer layer.

推荐答案

答:1):

一般来说流程紧密对应组织中的业务流程,而流程服务实现的任务更技术成分。

Generally speaking processes in the Business Process layer correspond closely to business processes in the organization, while process services implement more "technical" compositions of tasks.


  • 理论上在一个理想世界的情况下,应创建并通过图形用户界面与业务分析一些帮助商业用户自行修改业务流程,同时服务层的流程是由技术人员来实现。

  • 另一个区别是,很多时候,这些业务流程包括手动步骤 - 人们必须手工做的事,做主观的决定或确认/批准进程的继续。

  • 业务流程相结合的业务服务,同时服务水平的过程组成,往往会连接到多个后端系统,以做好自己的工作服务。
    举例:以订单履行的业务流程:您可能有需要的客户支持代理履行发出订单之前致电客户确认业务流程 - 这是一个手动步骤,这将是这一进程的一部分。然后,将完成启动后,称为服务层级进程评估客户的忠诚度级别可能被启动。因此,业务流程将执行类似履行客户订单的过程,而更多的技术服务进程将执行过程中,如比较相比,我们的商业智能商店当前正中该客户的信用等级 - 因此需要几个电话到多个后端系统。

答案2):

这是一个需要背景下,往往需要经验来做出正确的选择的区分,但这里是我的两分钱。

This is a distinction that requires context and often requires experience to make the right choice, but here are my two cents.


  • 如果你有一个地方的业务流程管理解决方案,并组织使用它,然后通过各种手段,实现在这一层的业务流程。这对于终端用户更加灵活和可以理解的 - 。您的企业

  • If you have business process management solution in place and the organization uses it, then by all means, implement any business processes in this layer. This is much more flexible and understandable for the end-user – your business.

如果您需要实现一个具有收集/从/在多个系统中修改数据的技术处理,然后实现它在业务层。当然,你可以尝试实施了服务层的业务流程(我已经在实践中有时会看到这一点)。但是,请记住,你将有一定限制的工具集,对比一下你将有一个真正的业务流程管理解决方案。您还可以在业务流程层,其在某些时候一个真正的BPM时可能不是很方便服务层,有的一些业务流程。所以这真的取决于你的面向服务架构的成熟状态。

If you need to implement a technical process that has to collect/modify data from/in multiple systems, then implement it on the service layer. Of course, you may try to implement business processes in the service layer (and I’ve seen this sometimes in practice). But keep in mind that you’ll have somewhat limited toolset, compared to what you will have in a real business process management solution. You will also have some business process in the service-layer and some in the business process layer, which may not be very convenient when having a real BPM at some point. So it really depends on the state of maturity of your service oriented architecture.

通常我会尽量避免在消费过程中实现。它使你的设计加上给消费者系统,所以你不能够在未来的时间点一样容易更换。此外,业务流程管理层(服务层)都具有用于监视,记录更好的手段等开箱即用。话虽这么说,在长期的维护和问题的调查将不会像在消费者应用程序一样痛苦。

Generally I’d try to avoid implementing processes in the consumer. It makes your design coupled to the consumer system, so you won’t be able to replace it as easily at a future point in time. Also, business process management layer (and service layer) both have better means for monitoring, logging and so on out of the box. That being said, in the long-term maintenance and problem investigation won’t be as painful as in a consumer application.

这篇关于关于SOA参考体系结构问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆