3 ms·
Valid point, and something I considered initially. However we've a security startup – the likelihood hood of us getting a huge wave of visitors, the hug of deat
by graystevens 9y ago
Valid point, and something I considered initially. However we've a security startup – the likelihood hood of us getting a huge wave of visitors, the hug of death, is highly unlikely. Our landing page is static & anything remotely intensive requires an account. We are more likely to be hit by a DDoS, which I would hate to consume by upscaling servers and burning any potential profits we have.
Additionally, I have multiple alerts setup for any signs of downtime, so that any deployment can be invoked as soon as possible.
However, I completely understand your perspective, and if this was a different type of startup or industry, I would probably implement it the way you mentioned.
- zenlikethat 9y agoI think you’re fine, personally — a workload has to have very well defined characteristics to be automatically scalable. Just paying when health checks fail and figuring out how to fix it when there’s a problem is a much better strategy than implementing “scaling automation” that might go awry.