Kind of, as I am using Mongrel2 and ZeroMQ, I cloned the repo and took a look at it.
ZeroMQ is a message passing toolkit with a lot of goodies where Pluton is to solve the concurrency problem, that is, when you generate a web page, you can access maybe 20 different services and merge the results in the page. If the 20 services requires each 5 ms to answer, you get 100 ms compute time when called in series, but imagine you can call the 20 in 2 batches, you can get an optimal 10 ms.
This what is provided by Pluton, a framework to call many services in parallel to improve the overall latency of your application from the end client point of view. Each small service run by default on the same system, but they can in return use ZeroMQ to communicate with other components.
The HTML documentation of the project is really good.
Comments
Kind of, as I am using Mongrel2 and ZeroMQ, I cloned the repo and took a look at it.
ZeroMQ is a message passing toolkit with a lot of goodies where Pluton is to solve the concurrency problem, that is, when you generate a web page, you can access maybe 20 different services and merge the results in the page. If the 20 services requires each 5 ms to answer, you get 100 ms compute time when called in series, but imagine you can call the 20 in 2 batches, you can get an optimal 10 ms.
This what is provided by Pluton, a framework to call many services in parallel to improve the overall latency of your application from the end client point of view. Each small service run by default on the same system, but they can in return use ZeroMQ to communicate with other components.
The HTML documentation of the project is really good.
Can we build a system above ZeroMQ for such purpose easily? I think the async semantic of ZeroMQ is suitable to mitigate the latency of multiple RPC.