#SPFestDC #Azure #Functions V2: What's new and getting started
Download as PPTX, PDF0 likes149 views
Slides supporting the session. Talking about Durable functions, Functions V2, telemetry, authentication and authorization, retry policies....
More Related Content
What's hot (20)
Similar to #SPFestDC #Azure #Functions V2: What's new and getting started (20)
More from Vincent Biret (20)
Recently uploaded (20)
#SPFestDC #Azure #Functions V2: What's new and getting started
- 1. Azure Functions: What’s New In V2 & Getting Started SharePoint Fest DC 2019 Vincent Biret
- 2. Passionate about technologies, development and community Vincent Biret @baywet bit.ly/vince365 Microsoft Office Dev MVP Azure and Office 365 developer @ 2toLead
- 3. Audience?
- 4. Agenda •Introduction to Serverless/Azure Functions •V2 improvements •Telemetry •Authentication & Authorization •Retry handling •Conclusion
- 5. Ready?
- 7. Improving the « pay for what you use » and the elasticity principles, it also provides a total abstraction of servers Serverless definition
- 8. Enable your team to deliver solutions faster, in a more structured way moving the focus on the business logic Benefits
- 9. Google Cloud Functions and AWS Lambdas are direct competitors of Azure Functions Offerings
- 10. Dozens of bindings/triggers available, no more need to build the boiler plate code! Connectors MS Graph
- 11. 5 languages supported for production in Azure Functions and more to come Languages (v2)
- 12. SKU’s & scale • Leverage App Service plan • Tiers: Free, Shared, Basic, Standard, Prenium • Cost based on reserved VMs • You have to manage scale • Comsuption based Plan • Cost Based # of Executions, Duration and Memory (GB.s)
- 13. Besides the browser, you can use VS2017/2019 + Azure SDK or VSCode + Azure F CLI Tooling
- 14. Creating a Function from the portal, from Visual Studio, from the CLI Demo
- 15. V2: What’s new and improvements
- 16. The separation of processes solved a lot of dependencies versions issues for dotnet Main improvements • Support for Java (version 8) • Transition to Dot Net Core 2 (from 4.7) • You must migrate from TextWriter to ILogger • Upgrade to Node 8/10 (from 6) • Separation of host process and running process • Extensions based model • Moved from Web Job Dashboard to Application Insights • Default timeout on ASE set to 30 minutes • Azure Durable functions
- 17. A common pattern to chain Azure Function was to use queues Coordinating Azure Functions: Chaining
- 18. A common pattern to chain Azure Function was to use a state repository, each function triggering the next one Coordinating Azure Functions: State Repo
- 19. The pain of coordinating Azure Functions grows exponentially with the number of functions. TRYING TO COORDINATE MANY FUNCTIONS
- 20. Durable Functions remove a lot of pain introduced with regular functions Introducing Durable Functions •All the benefits of « regular » Functions •Code defined workflow •Automates state management •Reports status •Enables new design patterns • Fan out/Fan-in • Chaining • Monitoring
- 21. The Orchestrator leverages a decorator design pattern to « work it’s magic » High level overview Orchestration client State persistence Orchestrator ActivitiesTrigger
- 22. Timers and external events allow to implement advanced scenarios like approvals, or deep integrations Timers and external events • Part of Durable Functions • Timers allow to set « timeouts » during execution • Avoids « active waiting » • External events allow processes outside of the Functions to influence the execution
- 23. Durable Functions, Timers, Events Demo
- 24. Tips and tricks
- 25. Application Insights is a key tool in understanding performance and stability of your functions. It should ALWAYS be enabled. Telemetry • Azure WebJobs Dashboard and Functions integration is being retired • Application Insight is the tool of choice • Set up sampling • Set up Daily cap • (when available) set up retention period
- 26. CORS are essential to comply with browsers security features when developing front end applications Local and production CORS • Azure App Service Environment provides support for CORS • When debugging locally you can configure host to support CORS • Local.settings.json
- 27. As http trigger functions are exposed to the web, it’s important to secure those. Authentication/Authorization • Using keys, existing policies: • Anonymous: anyone can access • Function: accepts host or function key • Admin: accepts host key • System: only accepts the master key • User: validates a use Auth (not working today) • Using bearer token validation (easy-auth) • Requires OAuth integration
- 28. It’s important to allow the function host to « understand » what is going on with your functions. This is why it is healthy to let your functions fail. Retry handling • Some triggers include default retry mechanisms • Eg: Service Bus, Event Hub,… • NEVER do active retry policies • ALWAYS let your functions fail • Azure Durable Functions include a passive retry mechanism for activities
- 29. Auth, Telemetry, CORS, Durable Functions retry policies definition Demos
- 30. Conclusion
- 31. Conclusion •More flexibility •Better telemetry •Easier Orchestration •Faster time to market •Money saved
- 32. Bit.ly/vince365 @baywet slideshare.net/VincentBIRET Thanks!/Questions? Vincent Biret Office 365 and Azure Developer, 2toLead @baywet Bit.ly/vince365
Editor's Notes
- #4: Mostly Devs and architects that want to know how to implement it. PMO and PMs who want to know how it’s done.
- #6: Gestion des questions, interaction, ok avec ce programme?
- #10: https://cloud.google.com/functions/ https://aws.amazon.com/lambda/ https://azure.microsoft.com/en-us/services/functions/
- #11: https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings Samples from Fabian: https://github.com/fabianwilliams/AzureFunctionsWithVisualStudio/tree/master/FunctWithFabs/FunctWithFabs
- #12: https://docs.microsoft.com/en-us/azure/azure-functions/supported-languages https://docs.microsoft.com/en-us/azure/azure-functions/functions-versions
- #14: https://aka.ms/FunctionsVsTools https://github.com/Azure/azure-functions-core-tools
- #26: https://feedback.azure.com/forums/357324-application-insights/suggestions/17454031-variable-data-retention-longer-or-shorter-than-th
- #28: The key can be passed using the code query string parameter or the x-functions-key http header https://vincentlauzon.com/2017/12/04/azure-functions-http-authorization-levels/ https://github.com/Azure/azure-functions-host/issues/33
- #32: Money save = dev time saved, less support to provide, better product/service