Of course. My point is, if it is something I depend on, I’d like it to fail flat on my face if it ever fails.
Case in the point: A few year ago, I have a system that often failed to deliver emails that contained the one time code for login purpose. (It was mis-configuration of some sort) I was grilled for it badly.
To recap, there are 3 ways to send emails:
- just send it in process
- spawn and send
- throw it out to a background job with pubsub, or oban if I want scalability or persistence across reboot.
1 has the easier error handling and is often fast enough. 3 has the latency and throughput advantage, 2 has none.
