Azure Functions and Blob Triggers: be careful on the binding type.
Azure Functions and Blob Triggers: Be Careful on the Binding Type This article discusses a problem that was recently discovered with Azure Functions and Blob Triggers. When using the string or byte array binding types, the content of the blob that triggers the function is fully loaded into memory, causing spikes in memory usage. This can be problematic when handling large blobs or multiple blobs concurrently. To solve this issue, it is recommended to use the stream or BlobClient binding types, as they allow for incremental processing of the blob. The article also suggests using Application Insights to monitor exceptions and provides a query for monitoring function app logs.
Article 17m
Login now to access my digest by 365.Training
Learn how my digest works
Features
- Articles, blogs, podcasts, training, and videos
- Quick read TL;DRs for each item
- Advanced filtering to prioritize what you care about
- Quick views to isolate what you are looking for right now
- Save your favorite items
- Share your favorites
- Snooze items you want to revisit when you have more time