.net - Using a queuing system to do custom logic -
i developing notification engine, notification engine send several types of notifications several receivers.
- email notification
- push notification
- ...
when client communicates notification engine in order send notification, engine must store notification in queue, before communicating receiver.
i have requirement flow should below:
- then notification engine must check if receiver able send notifications now.
- if receiver can send notifications, message sent it
- if receiver cannot send notifications, message must stay in queue, , try processed later.
for example, if sending email notification, email receiver running smtp server not accessible, receiver not able send email notification. notification should stay in queue, , processed later.
i know there several queuing systems may use msmq , rabbitmq.
what best practices can use in order develop logic , fulfill requirements?
Comments
Post a Comment