Bad dependency when hosting Twiml

[kevinburke]

Hosting the TwiML on the same infrastructure as the service being monitored is a bad idea, as an infrastructure failure would also take down your TwiML service and leave you in the dark for app notification.

It would be better to use something like Twimlets and just send the whole TwiML body in your initial API request.

It is still possible of course that the Twimlets service could go down. But if so, it's also likely that the Twilio service is down, which is an existing dependency problem. So you are reducing external notification dependencies from two to one.