comment-2008-12-12-1
by gpoul, 5604 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.
search
3 active users
- unknown (3)
backlinks (more)
none, yet
recent stores (more)
recent comments
echo earlZstrainYat|tr ZY @.
