We have a lot of background processing that happens in a web app and investigating ways to message users when a background task is complete. I'm wondering if anyone is using RabbitMQ for something like this and can describe their architecture.<div>
<br></div><div>We might have 20K concurrent users "logged in" at any given time. Some background tasks are important and the user must be notified, and for those we use the database. But, there's a number of other tasks that user can trigger where it's not critical that the user is notified, but would be nice to see. These would be very similar to "you have new mail" in a mail client, for example.</div>
<div><br></div><div>Questions that have come up is should message queues be session based or user based -- that is if you log into the web app with two browsers (or on two machines) would messages be broadcasted to all sessions for a give user or be session-specific, and how to deal with the non-persistent connections in web apps.</div>
<div><br></div><div> Anyone using RabbitMQ for this type of application?</div><div><br></div><div>Thanks,<br clear="all"><div><br></div>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org" target="_blank">moseley@hank.org</a><br>
</div>