3 ms·
Another technique to add to the mix if you can handle the additional complexity is to load or feature shed. If you can delay or just drop additional expensive a
by genxy 4mo ago
Another technique to add to the mix if you can handle the additional complexity is to load or feature shed. If you can delay or just drop additional expensive application features during the exact time you need to scale or handle a burst, then your system has additional core app logic to handle requests. This can prevent the system getting wedged in a positive feedback loop.
See also the gamedev technique of having sacrificial assets or code, so when you need to free up space late in the schedule to ship, you have something you can actually shed.
- Ylano 4mo agoHaving something intentionally non-essential to cut is much better than discovering under pressure that everything is load-bearing
- iTokio 4mo agoIt’s also an old devops trick to put some GB files on the FS of critical systems (databases, ..) when there are no way to dynamically add more space/volumes and monitoring is not trusted. Bit hard to explain though.
- genxy 4mo agoI think sacrificial ballast would be a good term, https://en.wikipedia.org/wiki/Ballast https://en.wikipedia.org/wiki/Ballast
- bijowo1676 4mo agosandbagging, nice trick. I know its used in project management, where you give conservative estimates to account for some necessary refactoring work (but never tell management you will be refactoring, cause they dont want to pay for that)