I don't really see point of Azure Functions as consumption plan suffers huge lag in booting time, and it often misses schedule and 20% of executions are missed or leads to timeout. Having fixed plan is as good as writing ASP.NET service on IIS with Web Jobs. I see premium plan coming up, but I bet it is expensive and still simple web service is far better.
There is more overhead on bookkeeping for billing rather than actual benefit.
I suggest MS to look on network functions, which runs in isolation as it has no access to local server, boot time issue can be resolved, functions should only access and process HTTP resource. As function will not access any local resource, there is no need to spin up a VM, many functions in isolation can be in side an active VM.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't really see point of Azure Functions as consumption plan suffers huge lag in booting time, and it often misses schedule and 20% of executions are missed or leads to timeout. Having fixed plan is as good as writing ASP.NET service on IIS with Web Jobs. I see premium plan coming up, but I bet it is expensive and still simple web service is far better.
There is more overhead on bookkeeping for billing rather than actual benefit.
I suggest MS to look on network functions, which runs in isolation as it has no access to local server, boot time issue can be resolved, functions should only access and process HTTP resource. As function will not access any local resource, there is no need to spin up a VM, many functions in isolation can be in side an active VM.