问题描述
读书面向服务架构原则网站和维基百科的各自的，我有一个想法：二郎山/ 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.
的唯一一件事是，Service在这样的系统中的每个服务合同是非常具体的。为了调用在二郎山/ OTP服务的编排层将不得不作出二郎通过邮件或电话调用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).
这不会让二郎神的/ OTP平台范围之内使该服务的任何电话。
This would not let making any calls to the services outside of Erlang/OTP platform scope.
但是，如果我们试图通过将所有相应的服务功能，成为一个基于Erlang的网络服务器，如受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?
这将允许从构成基于普遍服务合同规范砖头的各种应用。
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的协议。二郎山实现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.
在原则上，二郎神已经拥有一切为的的想法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：为什么不使用二郎山/ OTP Web服务器的服务？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！