[zeromq-dev] Efficient and reliable pub/sub mechanism

[Martin Sustrik]

Hi Yusuf,

 > By
> reliable, I mean that I want the engine to be resilient to individual
> system failure. So if process P publishes an event with a channel that
> process Q is subscribed to, and Q dies before it finishes processing the
> event, then P should persist the event. At some point in time, a process
> R will be created to take Q's place. It will notify P that it is the
> substitute, and P will send it the event.

There's no way to do that without distributed transactions. Try checking 
different distibuted transaction systems out there.

Martin