The other question is do you want persistant messaging ...To which i would say no ( in 95% of cases) ...good in theory , crap in the field and builds the expectation that things just work and when things go pear shape and it doesnt "just work" you dont have the systems that deal with failure.
But yes this has nothing to do with a transport. Ben On Wed, Apr 17, 2013 at 11:18 PM, Pieter Hintjens <[email protected]> wrote: > On Wed, Apr 17, 2013 at 4:58 PM, Jason Mulligan <[email protected]> wrote: > > > I'm preparing to have a MQ discussion with coworkers, and I was asked if > 0mq can use Cassandra for storage, for durability & and to lessen the > requirement for another database in play. > > > > So, my question is, has anyone looked into this? What did you find for > pros/cons? Is it too slow? > > > > If anyone knows where I could read up about someone's findings, that'd > be very helpful. > > Just to be clear here, 0MQ doesn't use anything for storage, it's a > transport layer. You'd write clients and workers and queues that used > 0MQ to connect to each other, and then use Cassandra (or whatever > storage) in the appropriate places where you wanted to hold state. > > So the question is really, "does Cassandra work well?" > > -Pieter > _______________________________________________ > 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
