I've had a lot of success persisting to an append only memory mapped file. A throughput of 300k/s 1kb size messages shouldn't be a problem. If you are on Java, I would suggest checking out the Chronicle queue from OpenHFT. I've used this in production in conjunction with ZeroMQ with fantastic results.
http://openhft.net/products/chronicle-queue/ -Trev On Wed, Oct 1, 2014 at 1:53 PM, Mohit Anchlia <[email protected]> wrote: > Our average message size is < 1k and we are looking at 300K per second. If > the solution is scalable then does it really matter? In other words by > adding more machines we should be able to scale brokers and workers. > > On Tue, Sep 30, 2014 at 10:55 PM, Pieter Hintjens <[email protected]> wrote: >> >> What kinds of throughputs and persistence are you looking for? >> >> On Wed, Oct 1, 2014 at 12:44 AM, Mohit Anchlia <[email protected]> >> wrote: >> > Are there any standard projects that users of ZeroMQ use today that >> > provides >> > persistence functionality as well? I am looking for a scalable ZeroMQ >> > persistence layer that is able to provide pub/sub and is tunable to be >> > non-persistent for async request/response. >> > _______________________________________________ >> > zeromq-dev mailing list >> > [email protected] >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
