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 platfor
This is our main application of Erlang: web services. We normally use Yaws Appmods and an article here can show you a lot on how its done. Erlang has been a good platform for SOA, because of the following:
1. Side Effect free code is very easilly written and tested.
2. Isolation: Processes in Erlang help isolate each service request in a clean way.
3. Most Erlang Libraries like mochiweb
, misultin
and Chicago Boss
have been built from ground-up to support SOA systems written in Erlang.
Its a great idea to apply your own OTP application behind any one of these frameworks. Another great reason why erlang is suitable for SOA is redundancy. SOA systems need to be up. If a service request fails, its re-tried along a different path (which, of course at physical layer, its being handled by a different machine where you OTP app has been distributed).
Give it a shot, great idea