Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Serverless Computing with Azure

410 views

Published on

Slides from my Global Azure Bootcamp (21st April 2018) talk on Azure Serverless Computing with main focus on azure functions.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Serverless Computing with Azure

  1. 1. Serverless Computing with Azurewith Azure Global Azure Bootcamp 2018 Analben Mehta
  2. 2. About Me Analben Mehta  Software Engineer at NHS NSS  13+ years of experience in architecting and developing enterprise applications  (Previously) creator of (Previously) creator of ProConnect – award winning product  M.Eng in Computer Science https://aanuwizard.com @aanuwizard
  3. 3. Agenda 1. What is Serverless? 2. Why Serverless? 3. Azure Functions – Intro 4. Demo4. Demo 5. Azure functions – Proxies 6. Demo 7. Serverless Scenarios 8. Demo 9. Azure Functions - Best Practices
  4. 4. No servers!!? “serverless” doesn’t mean servers are no longer involved. It simply means that developers no longer have to think that much about them.longer have to think that much about them. Ex. wireless switch / router – of course there are wires but users don’t have to worry about them.
  5. 5. Evolution of Infrastructure
  6. 6. Evolution of Infrastructure
  7. 7. What is Serverless?
  8. 8. Benefits of Serverless
  9. 9. Evolution of Application
  10. 10. Evolution of Application
  11. 11. Evolution of Application
  12. 12. Microsoft serverless offerings
  13. 13. Azure Functions Serverless code – triggered by events and bindings
  14. 14. Functions - Programming Model
  15. 15. Functions - Programming Model
  16. 16. Demo: Azure Function Demo – Getting Started
  17. 17. Supported Bindings Type Service Trigger Input Output Timer/Schedule Azure Functions ✔ HTTP (REST or WebHook) Azure Functions ✔ ✔ Blob Storage Azure Storage ✔ ✔ ✔ Queues Azure Storage ✔ ✔ Tables Azure Storage ✔ ✔ NoSQL DB Azure CosmosDB ✔ ✔ ✔NoSQL DB Azure CosmosDB ✔ ✔ ✔ Streams Azure Event Hubs ✔ ✔ Push Notifications Azure Notification Hubs ✔ Bot Framework(Preview) Azure Bot Service ✔ Twilio SMS Text Twilio ✔ SendGrid E-Mail SendGrid ✔ Excel Tables Microsoft Graph ✔ ✔ OneDrive Files Microsoft Graph ✔ ✔ Outlook E-Mail Microsoft Graph ✔ Microsoft Graph Events Microsoft Graph ✔ ✔ ✔ Auth Tokens Microsoft Graph ✔ (* The HTTP output binding requires an HTTP trigger.)
  18. 18. Supported Languages  Languages:  JavaScript, C#, F# scripting options such as Python, PHP, Bash, Batch, and PowerShelland PowerShell  Experimental support .NET Core Linux Containers Java
  19. 19. Functions pricing  Regular App Service plan  Consumption Plan Meter Price Free Grant (Per Month) Execution time* £0.000012/GB-s 400,000 GB-s Total executions* £0.15 per million executions 1 million executions
  20. 20. Azure Functions – Develop your way  Code directly in Azure portal  Code in Visual Studio 2017 15.5 or later Install “Azure Development” workload Includes tooling to create Azure Function projects andIncludes tooling to create Azure Function projects and classes locally and publish Includes Azure CLI (Command Line Interface) which allow you to run and debug your functional locally. Azure Functions extension for Visual Studio Code (Preview)
  21. 21. Azure Functions – Develop your way
  22. 22. Azure Functions Proxy vs API Management
  23. 23. Azure Functions – Proxy
  24. 24. Azure Functions – Proxy
  25. 25. Demo: Azure Function Demo – Mock Apis
  26. 26. Serverless Scenarios - Real-world examples
  27. 27. Timer-based processing
  28. 28. Serverless web application architectures
  29. 29. Azure service event processing
  30. 30. Serverless mobile back-ends
  31. 31. Demo: Azure Function Demo- Feedback application
  32. 32. Feedback system demo
  33. 33.  Functions should “do one thing”  Functions should be stateless  Functions should be idempotent  Functions should finish as quickly as possible Azure Functions – Best Practices  Functions should finish as quickly as possible
  34. 34. #GlobalAzureBootcamp @aanuwizard

×