330
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Feb 2024
330 points (100.0% liked)
Technology
37742 readers
511 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
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.
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.
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.