SOA：为什么不使用Erlang / OTP Web服务器作为服务？ [英] SOA: Why do not use Erlang/OTP web servers as services?

问题描述

阅读面向服务的架构原则网站和相应的维基百科文章我有一个想法：Erlang / OTP平台可以被认为是一个SOA平台，可以构建SOA应用程序。

After reading the Service Oriented Architecture Principles site and the respective Wikipedia article I had a thought: the Erlang/OTP platform can be considered as an SOA platform and SOA applications can be built on it.

唯一的事情是服务合同对于这种系统中的每个服务是非常具体的：为了在Erlang / OTP中调用服务，协调层必须通过Erlang消息或对gen_server的调用进行调用（取决于实现）。

The only thing is that the Service Contract for each service in such a system is very specific: in order to call a service in Erlang/OTP the Orchestrating layer would have to make calls via Erlang messages or calls to gen_server (depends on the implementation).

这不允许对Erlang / OTP平台范围之外的服务进行任何调用。

This would not let making any calls to the services outside of Erlang/OTP platform scope.

但是如果我们尝试通过将所有相应的服务功能移动到Erla来构建每个服务基于ng的Web服务器，如Mochiweb，并且基本上将gen_server的每个服务的接口更改为：调用XML？

But what if we try to build each Service by moving all the respective Service functionality into an Erlang-based webserver, like Mochiweb and essentially changing the interface of each Service from gen_server:call to XML?

这将允许从标准化的砖组成各种应用程序基于 WSDL 的通用服务合同。

This will allow to compose various applications from standardized 'bricks' with universal Service Contracts based on WSDL.

此外，这种方法将让我们继续使用OTP主管和其他OTP功能，因为这样一个服务仍然是一个OTP应用程序。

Moreover, this approach will let us continue using OTP supervisors and other OTP features, because such a Service will still be an OTP application.

所以，问题是：
您是否认为通过使用OTP Web服务器（Mochiweb）作为服务构建面向服务架构的软件应用程序是个好主意？额外的XML处理层可以消除这种方法的所有优点吗？

So, the question is: Do you think that building a software application with the Service Oriented Architecture approach by using OTP webservers (Mochiweb) as Services is a good idea? Can the additional XML processing layer destroy all the advantages of such approach?

推荐答案

这个没有做的主要原因是因为你会限制自己SOA协议。 Erlang通过一些附加点（监视器）实现IP协议。虽然你可以这样做，我想知道是否值得。

The primary reason this is not done is because you would limit yourself to the protocol of SOA. Erlang implements the protocol of IP with some added points (monitors). While you can do it, I wonder if it would be worth it.

原则上，Erlang已经拥有了想法的所有工具 SOA，但没有所有的膨胀的SOAP 和 WSDL ：）

In principle, Erlang already has all the tooling for the idea of SOA but without all the bloat of SOAP and WSDL :)

这篇关于SOA：为什么不使用Erlang / OTP Web服务器作为服务？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！