The Important Differences Between Blob Triggers and Event Grid Triggers in Azure Functions
Why Stack Overflow recommends it
Stack Overflow users link it when explaining why an Event Grid trigger is faster, more event-driven and more reliable than a Blob trigger for Azure Functions.
Recommended by 2 people across 2 different months, 2020 to 2021.
What it is
A short Microsoft DevRadio video comparing the two ways to run an Azure Function when a file lands in blob storage: the Blob Storage trigger and the Event Grid trigger. It walks through a demo and explains when to pick one over the other, with source code for the functions and a React SignalR client linked.
What people said
Recommends Matt Stannett · 2020-10 · Stack Overflow · on “Is it possible for Durable Azure Functions to communicate across programming languages (C# to Python Azure Functions)?”
Yes you could use the Function chaining pattern [LINK] in durable functions to do this since it only relies on the functions being within the same function app and uses the function names. However, you can achieve your end goal without the use of Durable functions by setting up your second function (which is currently triggered by a timer) by using an Event Grid trigger instead. Azure Event Grid allows you to easily build applications with event-based architectures. First, select the Azure resource you would like to subscribe to, and then give the event handler or WebHook endpoint to send the event to. Event Grid has built-in support for events coming from Azure services, like storage blobs
Recommends SauravDas-MT · 2021-10 · Stack Overflow · on “Trigger no longer cold starts Azure Function (Consumption)”
Yes. The event grid is event driven so whenever an event is fired it wakes up the azure function so it has higher success, you can check this video [this video] for the detailed difference between the two triggers. You can also check this document [LINK] to find the scenarios when we should use event grid trigger over the blob trigger.
Cites Harshita Singh · 2020-09 · Stack Overflow · on “Azure Functions BlobTrigger not firing for deleted blobs from container in azure storage account”
It is written "The Blob storage trigger starts a function when a new or updated blob is detected." here - [LINK] So, you cannot get deleted events in Blob trigger. Alternative for you is only to use Event Grid so that you get deleted events of blobs as well. In fact, Event Grid Triggers are faster than Blob triggers - [this video] Pricing: [LINK] It also won't require new code addition in your function app.
Cites Murphybro2 · 2020-11 · Stack Overflow · on “Blob trigger affecting application insight logging in azure functions”
I have two azure functions that exist in the same azure function app and they are both connected to the same instance of application insights: TimerFunction uses a TimerTrigger and executes every 60 seconds and logs each log type for testing purposes. BlobFunction uses a BlobTrigger and its functionality is irrelevant for this question. It appears that when BlobFunction is enabled (it isn't being triggered by the way), it clogs up the application insights with polling, as I don't receive some of the log messages written in TimerFunction. If I disable BlobFunction, then the logs I see in the development tools monitor for TimerFunction are all there. This is shown in the screenshot below. Time