Once deployed the Trigger functions are long running tasks that trigger on certain events is what I believe to be true.
To be precise, consider a scenario where I have deployed a Blob trigger which checks for file upload to blob storage.
After executing the trigger function. does my application still uses Host resources since it always listens to the blob storage for changes.
Is it like a websocket? Or the blob itself calls the function? Or what is it?
Is it the same with the timer trigger?
Just wanted to know if the resources are being used even after the triggers are already been executed.
Azure Function has Consumption and Premium service plans,
Also, The App service plan can be used for azure function too.
Consumption Plan: It charges based on the times your function has executed or ran; it will be shown as the
Y1plan name. For reference, you can check this Pricing calculator for functions, also mentioned in the document for consumption plan.Premium Plan: This plan has multiple options for instances, vCore, storage size. Each has different pricing; you can check it in Pricing calculator too.
Storage account is created with every function app and that will be charged differently based on usage. You can check the pricing for the storage account in the calculator.
For reference, check this Document.
No, the trigger function is not "always listening" in the same way that a WebSocket is. Instead, it's an event-driven function. It doesn't continuously consume resources while waiting for an event; it only runs when there is an actual trigger event.
I have created a timer trigger and blob trigger function in my Azure function. This is the accumulated cost for 20 runs and 5 runs for Azure storage, as shown below.
