4 ms·
Conceptually one lambda per page (route) sounds super cool, but in practice I suspect it would lead to a ton of cold start wait times for less common routes
by yodon 8y ago
Conceptually one lambda per page (route) sounds super cool, but in practice I suspect it would lead to a ton of cold start wait times for less common routes
- rozenmd 8y agoSounds like a trade-off for extreme scalability
- bpicolo 8y agoShouldn't change your ability to scale. AWS is happy to clone your single lambda an arbitrary amount of times.
- barbecue_sauce 8y agoThe tradeoff is the cold start wait time vs. easy scaling.
- yodon 8y agoYes, where needed, but I suspect for most people it's just a trade off of getting buzzword compliance in exchange for slow cold start responses
- matrix0978 8y agothese individual pages get compiled into a single file with zero dependencies leading to super fast cold start times. I'm a bot, beep boop.
- painful 8y agoHave you actually found cold-start delays to be an issue with serverless services, or are you just speculating? To my knowledge, the cloud provider keeps enough instances hot based on a forecasted demand. I have not found cold-start delays to be a real issue.
- zdragnar 8y agoI don't know if anything has changed since, but we definitely hot cold start perf issues on lesser used routes at a company I was with 18 months ago.
- scarface74 8y agoAWS doesn’t keep instances warm based on forecasted demand. It uses one instance per request and instances stay warm once they are started for a predetermined amount of time based on the size of tyrvlambda environment.
- reilly3000 8y agoIt depends on the stack. You have to be more mindful of cold start when running Java/Clojure apps, less with JS and .net. There are some good benchmarks out there. There are also some easy ways to keep routes warm, although for certain setups I imagine that could be quite expansive, though still probably not expensive.