4 ms·
Serverless is nice for running low traffic services for free. Azure Functions for example don't start charging until 1M+ executions IIRC. Transitioning to micr
by hypeatei 2y ago
Serverless is nice for running low traffic services for free. Azure Functions for example don't start charging until 1M+ executions IIRC.
Transitioning to micro services also makes serverless more appealing since you're getting a separate web server (resiliency) and scaling for free if you need it.
- alserio 2y agoI do agree for the use case of low traffic services but I've not tried Azure yet. What options do you have to avoid runaway costs and "denial of wallet" attacks?
- hypeatei 2y agoThe function app resource itself has a "Daily Usage Quota (GB-sec)"[0], but I'm not sure how useful it is since I've never used it. Overall billing management doesn't have a way to shut off the world if you go over, but alerts can be setup... basically the same as other clouds in this regard. You can also host functions apps on dedicated service plans and not "consumption" (serverless) plans which provides a predictable monthly bill without changing any of your code. 0: https://learn.microsoft.com/en-us/azure/azure-functions/functions-best-practices?tabs=csharp#maximize-availability https://learn.microsoft.com/en-us/azure/azure-functions/func...
- alserio 2y agoThank you!