[erlang-questions] Erlang microservice architecture ?

[Thomas Elsgaard]

>
> Except Thomas asked about micro services. I think you're talking about
> nano services. That hasn't been discovered yet.
>
> Garrett
>

I should maybe add that this is for low volume but complex service
activation in the telco domain, the current approach has been the
traditional SOA solution with an ESB and process orchestration (all Java
based), but the number of services has increased, and the ESB (service bus
+ message queue) is suffering from memory leaks and other stability
issues which is hard to troubleshoot, and in general, the solution is just
complex.

Now the buzz is microservices (someone might call it SOA 2.0) but i would
like to split the architecture up in smaller isolated services, and of
course Erlang based. My original idea was to split the services up on
separate servers, install yaws on each server, and then install Erlang
applications as yapps on each server. This means that i can autoinstall the
servers just with yaws, build Erlang apps and deployed them on the servers
as needed. I could host several yapps on the same server, and if needed,
move individual yapps to another server.

The communication between services would then be http based.

But is there an smarter solution ? Chandru had some good input for why not
using RPC (back pressure issue). Protobuffs via sockets could also work,
but requires some more work.

Fred is defiantly having some good input about just having all the
applications on the same VM, I could do that, it's better than the current
 Java ESB monster, but if I then decide to split the services to different
servers, it will require some re-write.

Anyone who has done anything similar ? I do not need high performance, but
i need to handle complicated business logic between many services, and of
course keeping it fault tolerant ;-)

Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150516/cc99b101/attachment.htm>