[jeroenhd]

> Do you want your clients failing to load your website at all? Is this the best approach to serving users?

There are good reasons for picking either. Large services under sudden load sometimes implement queueing, which is just failing but stylish.

For my blog posts, I'd rather throw an error than have people wait for thirty seconds. The contents aren't that important and the end result will probably look bad because of missing CSS anyway.

For API services, I'd want things to slow down rather than fail, unless failure is explicitly documented in the API and can be handled somewhat gracefully.