2 ms·
For email, that's why you set a relay within your control, that will accept messages without a fuss and send them around following SMTP conventions. But anyway
by marcosdumay 7y ago
For email, that's why you set a relay within your control, that will accept messages without a fuss and send them around following SMTP conventions.
But anyway, how is your application supposed to respond after any of those failures? Is it just supposed to ignore the failure and thread on like if nothing happened, leaving your users on the dark? Is it supposed to reliably log every task so that it can retry anything that fails and in the worst case feed failures into some monitoring system/process? Or is it supposed to inform the user of any success or failure before the user can move on?
Queue software is only a good match for the first. For the second you will need to roll your own interface with the monitoring system anyway, so it's much easier to roll your own queues and get control of everything. The third one is best done synchronous, it doesn't matter the nature of the process or how long it takes. But funny thing is, I have never seen the first situation on the wild.