Re: [Caml-list] Master-slave architecture behind an ocsigen server.

[Philippe Veber <philippe.veber@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]

Thanks Sébastien, a message broker layer could indeed simplify
communication between the server and the workers. I'll think of it if I
cannot use an higher-level API (dealing with a worker pool).


2013/3/27 Sébastien Dailly <sebastien-ocaml@chimrod.com>

> Le 26/03/2013 15:29, Philippe Veber a écrit :
>
>  Dear all,
>>
>> I'm developping an ocsigen website doing some scientific calculations.
>> Up to now, the calculations were done in the same process that runs the
>> server. In order to gain in scalability (and maybe stability too), I
>> would like to run those calculations in a separate (pool of)
>> process(es). As this is a pretty typical setup, I guess quite a few
>> people have already done that. So I'd like to hear some suggestions on
>> what library to use in this particular context. It seems to me that the
>> release library [1] should do the job and is lwt-friendly, but there are
>> maybe other good options?
>>
>>
> This make me think of the python celery project[1]. It rely on rabbitMQ
> for storing the task to execute and ensure persistance. The project just
> handle the message and give them to the registered worker.
>
> I found ocamlmq[2] wich could match, but didn't test it.
>
> [1] http://celeryproject.org/
> [2] https://github.com/mfp/ocamlmq
>
> --
> Sébastien Dailly
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/**arc/caml-list<https://sympa.inria.fr/sympa/arc/caml-list>
> Beginner's list: http://groups.yahoo.com/group/**ocaml_beginners<http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-**bugs<http://caml.inria.fr/bin/caml-bugs>
>

[-- Attachment #2: Type: text/html, Size: 2550 bytes --]