[zeromq-dev] high availability and persistance

[Sean Ochoa]

Hey all.  I've got two seemingly unrelated questions.

We're evaluating different message queuing technologies, and I have had the
pleasure of using zeromq recently.

1.)  One or more middle-ware messaging systems which utilizes zeromq as its
core component has recently (within the last year) experienced a high
availability failure.  How does one guarantee a high level of availability?

2.)  Could a system which utilizes zeromq as its core messaging component
also utilize a distributed non-relational data store like Apache Cassandra
to persist the information coming across the wire and so make the system
more durable?  And, if we did, would this totally bork the performance
benefits that switching to zeromq and a brokerless architecture buys us?

Many thanks to the community.

 - Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20110605/2fad22fb/attachment.htm>