Azure functions pitfalls
Download as PPTX, PDF0 likes186 views
This document discusses some pitfalls and lessons learned when using Azure functions. It covers poison messages in storage queues, binding problems with service bus and table storage outputs, quirks with HTTP triggers and logging exceptions, and good-to-know tips about NuGet packages, timer triggers, and configurations. The document is structured into sections on poison messages, binding problems, quirks, and good-to-know information related to using Azure functions.
1 of 6
Download to read offline
Azure functions pitfalls
- 1. Azure functions Patrick van Ek Pitfalls & Lessons learnt
- 3. Poison messages Storage queues behave differently in Azure functions
- 4. Binding problems Service bus output like String, results in autodetected content type Table storage output ITableEntity cannot replace item Blob trigger uses logfile for triggering which makes it very slow Recently fixed!Blob trigger uses logfile for triggering which makes it very slow Timer triggers, uses cron-extention Parameters and their syntax in signatures
- 5. Quirks HttpTrigger social login Exceptions truncated in logs Concurrent processing of trigger functions Consumptionplan vs service plan
- 6. Good-to-knows NuGet packages Next execution of timer can be found in blob Web.config Reverse proxy Some intellisense in Visual studio Also an app-service Host.json Webjob-SDK