2 ms·
> Case in point: the concept of a service plan. It's straight up stupid to have a so-called cloud provider force customers to manage how many instances packing
by p_ing 1y ago
> Case in point: the concept of a service plan. It's straight up stupid to have a so-called cloud provider force customers to manage how many instances packing X RAM and Y vCPUs you need to have to run a function-as-a-service app, and then have to manage how that is shared with app services and other function apps.
You're not forced to, you can use a consumption plan.
https://azure.microsoft.com/en-us/pricing/details/functions/?cdn=disable#pricing https://azure.microsoft.com/en-us/pricing/details/functions/...
- motorest 1y ago> You're not forced to, you can use a consumption plan. Pray tell, what do you think is relevant in citing how many plans you can pick and choose from to just run a simple function? I mean, are you trying to argue that instead of one type of plan, you have to choose another type of plan?
- deleted 1y ago[deleted]
- p_ing 1y agoThe consumption plan is the default plan, so technically you don't have to choose anything, just go with the defaults. But it disproves your point that you're "forced" to have an app service plan. At this point you're simply arguing to argue after having been shown to be incorrect multiple times. Good luck.