In another comment I mention that our service has some properties which make this a great solution. It doesn't always work, but when it does, it's awesome. To

In another comment I mention that our service has some properties which make this a great solution. It doesn't always work, but when it does, it's awesome. To your point, Erlang has the concept of supervisor trees and handling of errors. Similarly, our supervisor is the Lambda runtime. If everything goes wrong, the runtime will emit a metric error. But what if Lambda itself fails? Or Cloudwatch? or any other supporting service? of course this is possible. But probably at that point the system is so fucked up that the fate of our little service is of little relevance. At least we know from past outages that when normal operations resume, the system will correct itself.