start | find | index | login or register | edit
by gpoul, 4126 days ago
Please enlighten me. In what cases does an asynchronous in-memory queue service make sense?

I mean don't get me wrong. I can see why in-memory databases make sense. I can see why queueing makes sense if I wait for it to complete to answer a user transaction, we're using that quite frequently for payment backends and stuff, but an asynchronous in-memory queue service just doesn't do it for me. What happens when the stuff dies. Do I have to scan my whole data to find what async processes didn't complete to restart them after a crash? I don't really get it.
powered by vanilla
echo earlZstrainYat|tr ZY @. • esa3 • online for 6967 days • c'est un vanilla site