Am Donnerstag, den 04.12.2014, 15:37 +0000 schrieb Malcolm Matalka:
> It depends on what level you're talking.  My distributed systems apps
> tend to be functorized over their transport, so I can switch out what
> works and what doesn't pretty easily.
> 
> I tend to avoid RPC frameworks, I find they focus more on the
> computation than on the data, but depending on what you're doing they
> could be appropriate.
> 
> Unless you're under heavy load, simple HTTP calls with some JSON is
> probably sufficient.

I guess Francois is asking because for some reason HTTP is
inappropriate. I can understand that because it is a really bloated
protocol, and you usually only use it when you need to (e.g. you have to
call it from Javascript or the like, or have to go through firewalls).
Also, there are several aspects you cannot control well, e.g. when TCP
connections are created and kept alive (or not). Multicast messaging is
completely impossible.

I recommend to not to see RPC systems under their framework aspect, but
simply as transport libraries. In particular, if you don't like the
serialization scheme, there is usually the alternative that you take
your own serializer and just send the data as (binary) strings on the
RPC level (which is always possible and simple to do). From my
experience it is essential that you have good control over the low-level
things (e.g. connection control, timeouts, retrials, error handling
etc), because this is what the distributed system keeps running. Sure it
is good when an RPC library implements some automatisms (e.g. for error
handling), but it is even better when there is also a manual mode, as
distributed systems sometimes require unusual ways of dealing with that
stuff.

Gerd

> 
> Francois Berenger <francois.berenger@inria.fr> writes:
> 
> > Hello,
> >
> > If you know about some distributed application that went into production
> > and that can happily withstand the fire of production and real world loads, I would be happy to here about which library the system was
> > using.
> >
> > I have heard about MPI and zmq for example, which both have
> > ocaml bindings. However, I also know that there are several RPC
> > implementations out there (one in ocamlnet, one in mirage, one in core), but I am not sure about which one is the most mature and
> > production-tested.
> >
> > Thanks a lot,
> > Francois.
> 

-- 
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
My OCaml site:          http://www.camlcity.org
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
------------------------------------------------------------