Download to read offline
Uploaded byMichelangelo van Dam
Moving from app services to azure functions
The document narrates the transition from traditional app services to Azure Functions, highlighting challenges faced with previous bare metal and cloud server approaches, such as high costs and maintenance issues. The author emphasizes the benefits of platform as a service (PaaS) offered by Azure, including automation, managed containers, and event-driven serverless computing. Key takeaways include the importance of loosening code bases and consistently exploring better solutions in technology integration.
More Related Content
Similar to Moving from app services to azure functions
Moving from app services to azure functions
- 1. Moving from AppServices to Azure Functions A story of how we increased our throughput on Azure 1
- 2. Michelangelo van Dam Co-founder/CEOIn2it PHP Community Leader Open source contributor CoderDojo Coach MVP Azure Moving from App Services to Azure Func5ons 2
- 3. How we didthings in “the old days” Bare metal servers in local DC Optional virtualisation Manual deployments Releases after office hours Moving from App Services to Azure Func5ons 3
- 4. Moving from App Services to Azure Func5ons 4 Web App MySQLDB Redis Cache Shared FS
- 5. Release drama Broken packages De-syncbetween staging and production servers Network issues Hardware issues Moving from App Services to Azure Func5ons 5
- 6. We needed bettersolutions! Moving from App Services to Azure Func5ons 6
- 7. Discovery of thecloud in 2006 Moving from App Services to Azure Func5ons 7
- 8. It worked outinitially… VM’s for test, staging and production that were equal Storage on S3 Moving from App Services to Azure Func5ons 8
- 9.
- 10. … but weencountered some cons No cloud native database support Very pricy for the services provided Still lots of maintenance to keep our VM’s up-to-date Moving from App Services to Azure Func5ons 10
- 11. Managed services Infrastructure supportfor Java, .Net and Ruby Very costly on top of expensive AWS bills Lots of restrictions on what was possible Moving from App Services to Azure Func5ons 11
- 12. We needed bettersolutions! Moving from App Services to Azure Func5ons 12
- 13. 2008 Windows Azure introby Josh Holmes at MS Belux Moving from App Services to Azure Func5ons 13
- 14. Windows Azure waswhat we needed! Platform as a Service You manage your app Microsoft takes care of the platform and infrastructure Separate services for database, cache and much more Supported open source Moving from App Services to Azure Func5ons 14
- 15. Automation! Azure allowed usto fully automate the deployment processes Moving from App Services to Azure Func5ons 15
- 16. Moving from App Services to Azure Func5ons 16 Classical WebApplication Configuration West Europe PHP Azure Services Azure SQL Storage Blob Storage Queue Sendgrid Services North Europe PHP Azure Services Azure SQL Storage Blob Storage Queue Azure Load Balancing Replication
- 17.
- 18.
- 19. Some challenges Docker containersare immutable Persistence must be kept outside containers Not a lot of examples and sources for best practices Moving from App Services to Azure Func5ons 19
- 20. Moving from App Services to Azure Func5ons 20 PersistentFile Sytem Web FrontWeb Front Web Front Web Front PHP-FPM PHP-FPM PHP-FPM Worker Worker Worker
- 21. Say hello toKubernetes Moving from App Services to Azure Func5ons 21
- 22. Managed containers onAzure AKS simplifies deployment and operations of Kubernetes Dynamically scale application infrastructure Security provided by Azure AD and Key Vault Cost effective platform for container infrastructure Moving from App Services to Azure Func5ons 22
- 23. Moving from App Services to Azure Func5ons 23 Internet Azure AKS PODPOD SCM CI/CD AKS Node Azure Container Registry
- 24.
- 25.
- 26. Azure Functions ina nutshell Event-driven serverless compute platform Build and debug locally Deploy and operate at scale on Azure Integrate services using triggers and bindings Moving from App Services to Azure Func5ons 26
- 27. Inspired by Mr.Hunt https://in2.se/hipb-serverless Moving from App Services to Azure Func5ons 27
- 28. We want thattoo… but how? Moving from App Services to Azure Func5ons 28 🤔
- 29. Where could weimplement functions? Most requests from customers: product details ✓ Most requests from employees: order and support tickets ✓ Most viewed page: sales and shipment dashboards ✓ Moving from App Services to Azure Func5ons 29
- 30.
- 31. How to getstarted? Download the Azure Functions Core Tools Moving from App Services to Azure Func5ons 31 https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local
- 32. Supported Technologies Moving from App Services to Azure Func5ons 32 TechnologyV1 V2 C# GA (.NET Framework 4.7) GA (.NET Core 2) JavaScript GA (Node 6) GA (Node 8 & 10) F# GA (.NET Framework 4.7) GA (.NET Core 2) Java N/A GA (Java 8) Python Experimental Preview (Python 3.6) TypeScript Experimental GA (supported through transpiling to JavaScript)PHP Experimental N/A Batch (.cmd, .bat) Experimental N/A Bash Experimental N/A PowerShell Experimental N/A
- 33. So how doI get started? Create a directory Init a “func” project Write your logic Run & Test locally Push to Azure Run it Moving from App Services to Azure Func5ons 33
- 34.
- 35. The impact ofmoving to functions Moving from App Services to Azure Func5ons 35 0 480 960 1440 1920 2400 Sep 18 Oct 18 Nov 18 Dec 18 Jan 19 Feb 19 Mar 19 Apr 19 switch containers ➤ functions
- 36. Our serverless journeyhas just begon Moving from App Services to Azure Func5ons 36 DONE TO DO Product details Procurement Incoming Orders Shipping Callback requests Customer history KPI Dashboards Stock management Portal advertisements Customs declarations Commercial mailings Content management Import regulation management
- 37. Some takeaways Prepare forthe “next best thing” and have a loosely coupled code base Always experiment! It might be good today, but can it be better tomorrow? Azure offers all required tools to get started, but choosing the “right” tool is the hardest part Moving from App Services to Azure Func5ons 37
- 38. Our most importantlessons Do not create a new client with every function invocation (RTFM) Fail early by keeping timeouts as small as possible Moving from App Services to Azure Func5ons 38
- 39.
- 40.