Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's fairly common with serverless functions - folks will start a project on serverless, expecting very little traffic.

Eventually, they get lucky, and their Lambda functions are running non-stop, incurring a fairly large premium over a normal constantly running VM.

I managed to do this with my side project (AWS bill in the several hundred dollars per month range), I wrote about it here: https://onlineornot.com/on-moving-million-uptime-checks-onto...



Can you explain in simple words what does it means? I can see in many sites that they recommend using lambda for saving , and now you say that when you get lucky and grow the bill will explode?


Keeping a server running costs you X/hour. Having a lambda costs you Y/invocation. Which is cheaper depends on the number of invocations per hour. If you have 1 invocation per hour, a lambda will be cheaper. If you have 2 million per hour, a server might be cheaper.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: