is recommended have .net web application rabbitmq producer?
i asking because not recommended have rabbitmq consumer insider iis web application : https://stackoverflow.com/a/25571635/2107373
in case, asp.net web application hosted on iis , runs behind load balancer (multiple instances).
we have web application queues messages onto rabbitmq consumed different application on backend , don't experience issues.
the problems mentioned in question refer unreliability of iis app pool's not being available consume messages shouldn't issue if handle of work in creating , queueing message within scope of user's request.
if case request either processed successfuly - message created , queued , confirmation response sent or there error - no message sent , user notified way of different response.
the biggest challenge had handling possibility of duplicate messages sent - in our case had check on consuming application make sure work wasn't done twice , tied rabbitmq producer scope of underlying (sql) database transaction sent on successful commit.
there's useful answer here advantages of using rabbitmq mechanism implement backend job processing: use of messaging rabbitmq in web application?
Comments
Post a Comment