Yeah but then you have a customer calling and screaming at you “We just launched our big sale of the year and our site has been down for an hour!!!”.
If you let them burst and bill them, you end up with angry clients. If you don’t, you end up with angry clients. Letting them burst and being forgiving with the bill is the better approach IMHO.
You advice probably doesn’t apply to the OP in the image, as a “simple static site” is probably their blog or project wiki. It’s very unlikely they even have clients. For that case just having a hard limit and waiting is much safer.
I mean, I get email notifications as I’m approaching the threshold so I’m never caught off guard unless I ignore those. If everything’s legit (e.g. no DDoS), I can just add extra egress bandwidth with no interruptions.
Yeah but then you have a customer calling and screaming at you “We just launched our big sale of the year and our site has been down for an hour!!!”.
If you let them burst and bill them, you end up with angry clients. If you don’t, you end up with angry clients. Letting them burst and being forgiving with the bill is the better approach IMHO.
You advice probably doesn’t apply to the OP in the image, as a “simple static site” is probably their blog or project wiki. It’s very unlikely they even have clients. For that case just having a hard limit and waiting is much safer.
I mean, I get email notifications as I’m approaching the threshold so I’m never caught off guard unless I ignore those. If everything’s legit (e.g. no DDoS), I can just add extra egress bandwidth with no interruptions.
Is there a customer involved here?
After all if it’s for a customer it might be better to just give them the choice since the bill is on them.