search

COCPORN / succubus

An event library.
MIT License
6 stars 1 forks source link

Durability #14

Open kellyelton opened 9 years ago

kellyelton commented 9 years ago

Is there any work in this library to handle message durability?

COCPORN commented 9 years ago

Hi, Kelly!

What exactly are your requirements?

Succubus is a relatively young library, and I would recommend you don't use it in production, even if i do. On Apr 26, 2015 8:58 PM, "Kelly Elton" notifications@github.com wrote:

Is there any work in this library to handle message durability?

— Reply to this email directly or view it on GitHub https://github.com/COCPORN/succubus/issues/14.

kellyelton commented 9 years ago

Well some libraries go pretty far with durability. Such as storing messages on the file system until they can confirm they are delivered etc. I know NetMQ(or zeromq, whichever you're using) don't have any mechanisms to say "this message was delivered". If a message isn't delivered, it would retry etc.

I'm just wondering if anything like this is in place, and if so, to what extent.

COCPORN commented 9 years ago

I am out drinking right now, but i will try to address the question tomorrow.

What happens in terms of durability is up to the backend. Writing a backend for, say, msmq, our azure service bus is almost trivial. They have the durability you want. On Apr 26, 2015 9:12 PM, "Kelly Elton" notifications@github.com wrote:

Well some libraries go pretty far with durability. Such as storing messages on the file system until they can confirm they are delivered etc. I know NetMQ(or zeromq, whichever you're using) don't have any mechanisms to say "this message was delivered". If a message isn't delivered, it would retry etc.

I'm just wondering if anything like this is in place, and if so, to what extent.

— Reply to this email directly or view it on GitHub https://github.com/COCPORN/succubus/issues/14#issuecomment-96421646.