3 ms·
Autoscaling, available on most popular clouds/hosts
by smt88 4y ago
Autoscaling, available on most popular clouds/hosts
- _448 4y agoI should have added, "for a side-project, and on the cheap" :)
- smt88 4y agoMake as much of the app static as possible. Run as much of the logic in the browser as possible. Once you've isolated the "must be on the server" stuff, put an intelligent rate limit on it, add auto-scaling with upper limits, and prepare a page to be shown when the server goes down.
- sprobertson 4y agoHighly dependent on your stack but there are plenty of free tiers for most serverless services. E.g. if you're willing to write everything in JS/TS then Vercel is a great option. (Kind of relevant to your post about adapting architecture to cost)
- smt88 4y agoThe problem with serverless is that the failure mode for traffic spikes is either "shockingly high bill" or "stops serving requests". For high, sustained load, a running server is always cheaper, the cost is predictable, and the failure mode is usually "serving requests much more slowly".
- throwawayadvsec 4y agoAWS lambda seems dirt cheap, or am I mistaken?
- smt88 4y agoIt's not that hard to accidentally have a huge bill if you get overloaded with requests.