O365Con18 - Automate your Tasks through Azure Functions - Elio Struyf
1 like82 views
This document discusses Azure Functions and serverless computing. It provides an overview of Azure Functions, including how they can be used for scheduled tasks or triggered by events. It compares Azure Functions to Web Jobs and outlines pricing plans. The document also covers security options, local development, using bindings, and deployment. It demonstrates how to write a first Azure Function and discusses troubleshooting and next steps like durable functions.
O365Con18 - Automate your Tasks through Azure Functions - Elio Struyf
- 1. Elio Struyf Architect @ Valo – MVP November 15th, 2018 Automate your tasks through Azure Functions
- 4. No hamsters are involved in the process of running your functions
- 5. #SPSOslo - @eliostruyf What is Serverless? • Abstraction of servers • AKA: FaaS (Function as a Service) • Event-driven / instant scale • Pay-per-use • Micro-services → decouple monolithic applications • No permanent storage, or it has to live somewhere else
- 7. Azure Functions • Running pieces of code / scripts in the cloud • Use the language of your preference • Runs on Azure App Services Use cases • Timer function • Call from SPFx web part • Call from site design / flow • …
- 8. Azure Functions vs Web Jobs Similarities • Both can be scheduled or use a trigger (queue/blob/etc.) • Both support C#, JavaScript, PS Differences • Pricing • Development flexibility • Easier to call Azure Functions (HTTP Trigger) • It has its own UI in Azure • Restrictions: 10 minutes timeout
- 9. Azure Functions – Pricing plans Consumption plan • € 0,17 per one million requests • Scales up automatically • Useful for smaller workloads • Max. timeout of 10 minutes App Service Plan • Depends on the chosen plan • You’re in control of scaling • Faster / higher workload • Timeout: 30 min. (can be unlimited) Turn on: always on!host.json { "functionTimeout": "00:10:00" }
- 10. What to know before you start creating them • Functions should be stateless • Function app can only use a single language • Think about what triggers are required for your functions • Need to call your functions from an application, try using ngrok • Avoid long running operations / split them in multiple ones
- 11. #SPSOslo - @eliostruyf Demo: Checking out the portal
- 13. Security options Simple function authentication • A code passed to the function • On function level or app/admin level https://<app-name>.azurewebsites.net/api/<function>?code=<code> Azure AD Authentication • Use OAuth token to call the function • Great use in combination with SPFx solutions: AadHttpClient
- 15. Local development options Any stack / editor / platform • azure-functions-core-tools • Node.js Visual Studio • True C# functions • Azure development workload
- 16. Useful CLI commands • func init → initialize a new project • func new → create a new function • func host start → start up the functions runtime • func azure functionapp fetch-app-settings <function-name> • func azure storage fetch-connection-string <storage-name>
- 17. Debugging your functions • Run: func host start • Press F5 in Visual Studio Code and execute your function
- 18. #SPSOslo - @eliostruyf Demo: Writing your first Azure Function
- 20. #SPSOslo - @eliostruyf Importing dependencies • Node.js → npm install • Make sure you create a package.json file (npm init) • Best to be placed on the root level • C# • Use NuGet like you are used using it Function A function.json index.ts node_modules Function B function.json index.ts node_modules package.json node_modules
- 21. #SPSOslo - @eliostruyf Working with environment variables
- 22. #SPSOslo - @eliostruyf Working with environment variables • Local development: local.settings.json • On Azure: Application settings In code • Node.js • process.env.<setting-name> • C# • GetEnvironmentVariable("<setting-name>")
- 24. #SPSOslo - @eliostruyf Working with bindings Blob storage Cosmos DB Storage queue Service bus HTTP … Input Blob storage Cosmos DB Storage queue SendGrid Twilio … Output Function
- 25. Queues are great for… Anything that should be picked up by a longer running task • SharePoint site provisioning • SharePoint web hooks • File processing (e.g. image size optimization) QueueTrigger function • Auto-runs your code when a message gets added • If fails, it retries
- 26. Queues are great for… Item 1 Item 2 Item 3 Item 4 Item 5 Item 6 Queue triggeredHTTP Triggered Item 1
- 27. #SPSOslo - @eliostruyf func extensions install
- 28. Working with bindings Add your bindings to the function.json file { "disabled": false, "bindings": [{ "authLevel": "function", "type": "httpTrigger", "direction": "in", "name": "req" }, { "type": "queue", "name": "spfxversions", "direction": "out", "queueName": "versions", "connection": "AzureWebJobsStorage" } }
- 29. #SPSOslo - @eliostruyf Demo: Creating settings and bindings
- 31. Deployment options • Publish from Visual Studio • CLI: func azure functionapp publish <function-name> • Use local GIT repository • Continuous deployment via Azure DevOps
- 32. Do not forget to configure your settings
- 33. #SPSOslo - @eliostruyf Cold start
- 34. What happens during a cold start Azure allocates server Worker becomes specialized Function runtime resets Function loaded into memory code runs
- 35. When function is already warmed-up Azure allocates server Worker becomes specialized Function runtime resets Function loaded into memory code runs
- 36. Optimizing the cold start • KISS • Precompile C# created functions • Not use the *.csx files • Use Visual Studio + Azure development workload • Use Azure Functions Pack for Node.js • https://github.com/Azure/azure-functions-pack • Uses Webpack • Add your dependencies at root level of the host!
- 37. #SPSOslo - @eliostruyf Demo: Deployment via local GIT repo
- 39. #SPSOslo - @eliostruyf Troubleshooting Check the linked Application Insights Check Kudu (advanced tools) Push debug build (only in DEV - slots) & attach the VS remote debugger Try to reproduce it in your local version
- 40. #SPSOslo - @eliostruyf What’s next?
- 41. #SPSOslo - @eliostruyf Durable functions • Extension on top of Azure Functions and WebJobs • Write stateful functions • Waiting for human interaction
- 42. Questions?
- 43. Office Servers & Services MVP Azure / Office 365 / SharePoint @eliostruyf www.eliostruyf.com [email protected] Elio Struyf Developer & Architect