Re:AWS and Azure Are at Least 4x–10x More Expensive Than Het...
by CharlieDigital on Monday October 21, 2024 @07:36AM
(#41903020)
Neither Fargate nor App Runner scale to zero (unless something changed). So there is always a baseline cost of a few dollars.
[ Parent
| on HN ]
Re:AWS and Azure Are at Least 4x–10x More Expensive Than Het...
by chrisoverzero on Monday October 21, 2024 @08:18AM
(#41903347)
But if you’re constantly pinging the container (as suggested above), it will never scale to zero.
Re:AWS and Azure Are at Least 4x–10x More Expensive Than Het...
by CharlieDigital on Monday October 21, 2024 @08:55AM
(#41903660)
It "scales to zero" as soon as the request stops as far as billing is concerned.
However, the image remains "warm" and incurs zero cost once the last request ends. So I usually have a `/heartbeat` endpoint for this purpose and point a Cloud Scheduler job at it.
I haven't read the docs to figure out the exact heuristics of when it becomes "cold" again.
Re:AWS and Azure Are at Least 4x–10x More Expensive Than Het...
by obenn on Monday October 21, 2024 @07:41AM
(#41903050)
Lambda container would be the closest equivalent with that functionality, https://docs.aws.amazon.com/lambda/latest/dg/images-create.h...
Re:AWS and Azure Are at Least 4x–10x More Expensive Than Het...
by paulvnickerson on Monday October 21, 2024 @08:30AM
(#41903450)
Agreed. I ran a small GPT chatbot on Lambda through API Gateway with a dynamodb storage backend and don't recall incurring any cost (or if I did, was just pennies per month).