What Kind of Asynchronous Is Right for You?
&gt; a failure of one service does not cascade and degrade the functionality of all other services using it.<p>This always struck me as a blatantly disingenuous generalization.<p>What are the two services being described here? It matters very much.<p>If my product is an email platform, and the &quot;API service&quot; accepted the &quot;send email&quot; request by enqueuing a &quot;send email&quot; message for the &quot;email sender service&quot;, if the &quot;email sender service&quot; is down, it absolutely does degrade the experience of API service users: &quot;your email is sent&quot; vs &quot;your email will be sent as soon as we&#x27;re able&quot; is two very different promises.<p>I think I&#x27;d like to work for the company who doesn&#x27;t care about the difference in those two promises. It&#x27;d be very easy to just implement the worst possible solution and provide the flakiest possible experience. Of course, I haven&#x27;t seemed to find those employers yet in my career. Everyone wants reliability and performance and everything else that sounds nice, all without specifying how the product should really behave. Where are the companies where I can implement these brilliant solutions without the downsides?