Serverless on Azure with Functions
•Download as PPTX, PDF•
0 likes•639 views
Slides used for my Shropshire User group talk
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Serverless on Azure with Functions
Similar to Serverless on Azure with Functions (20)
More from Christos Matskas
More from Christos Matskas (20)
Recently uploaded
Recently uploaded (20)
Serverless on Azure with Functions
- 1. Serverless with Azure Functions Christos Matskas
- 2. PaaSIaaSOn-Premises The evolution of application platforms Serverless
- 3. Event-driven/ instant scale Micro-billingAbstraction of servers What is Serverless?
- 4. Benefits of Serverless Reduced DevOps Manage apps, not servers Faster time to market
- 5. Serverless application platform components PlatformDevelopment Local Development Monitoring Integrated DevOps Visual Debug History IDE support</>
- 6. Demo Using Functions in the Azure Portal
- 7. Running Functions Pay only for what you use! Metering is per execution and per GB Second. Your own dedicated cloud environment with network isolation for apps, higher scale, and the ability to connect securely to local vNets. All the advantages of Functions with the SLA and ‘always on’ features of an App Service Plan.
- 8. Embracing new scenarios Totally portable Run on Functions on Linux with our containers, BYOC, Use Kubernetes or Service Fabric Leverage cloud innovations in on-premises infrastructure. Azure Stack brings the power of Azure to your own data centers. Run your Azure Functions on your local server (without the rest of Azure)
- 11. More bindings Built-in EnterpriseOn-premise Over 190 LogicApp connectors and ever expanding EventGrid events
- 12. Azure Functions Bindings Extensibility Goodbye SDKs, hello bindings!!
- 14. Deployment and management isolation Customers Products Orders API calls customers.azurewebsites.net products.azurewebsites.net orders.azurewebsites.net
- 15. Function app A /customers Function app B /products Function app C Function3/orders Function1 API proxy endpoints HttpTrigger function endpoints Key: /products /orders Function2
- 16. Serverless APIs Proxies Security (EasyAuth) OpenAPI (Swagger) CORS (Cross Origin Resource Sharing) Flow & PowerApps integration API Management
- 17. Function app A /time Function1 / /movies
- 18. Tools Windows MacOS Linux Portal (with Kudu) Visual Studio Visual Studio Mac Visual Studio Code Function Core Tools
- 19. App Insights VS, VS Mac, VS Code Azure Functions Core Tools VSTS, Maven, Kudu GitHub, BitBucket, Jenkins
- 21. Monitoring with Application Insights Monitor What is my app doing? Alert Is my app unhealthy? Diagnose Why is it unhealthy? Learn What was my app doing?
- 22. aka.ms/cmdemo
- 23. Azure Functions is an Open Source project https://github.com/Azure/Azure-Functions Azure WebJobs SDK script the Azure Functions runtime Azure WebJobs SDK the "core" of the Azure Functions runtime and many bindings Azure WebJobs SDK extensions the repositories of many bindings Azure Functions CLI the command line tool for Azure Functions Azure Functions Portal the UX for the Functions development portal Azure Functions templates the templates which show up the Azure Functions portal Azure Functions samples repository for some samples on how the runtime works
- 24. Interested? Check out these workshops
Editor's Notes
- “What is serverless?”
- Abstraction of servers, infrastructure and configuration of operating system Event-driven scale Sub-second billing Stateless Serverless compute is a fully managed service. Some refer to it as Functions as a Service OS and Framework patching is performed for you There is zero administrative tasks and no need to manage any infrastructure You just deploy your code (function) and it runs Your code runs within seconds and for very short period of time Serverless compute scales quickly (almost instantly) and vastly Automatically scales within seconds No scale configuration is required (there is no way to configure scale or limits) Scales to match any given workload. Scales from zero to handle tens of thousands concurrent functions invocations within seconds Pay only for the time your code is running Serverless compute reacts to events React, in near real-time, to events and triggers Triggered by virtually any event from Azure service or 3rd party services
- “Pinnacle of PaaS compute” Not just hardware “servers”, but software servers are also managed for you Focus on business logic, not solving technical problems not core to business Lower effort to get started makes it easier to experiment (bots, etc.) Benefits of “Serverless”
- Azure’s serverless picture
- First, a simple event hub JS function (just trigger) Then, a good example of a C# function with a trigger and input/output bindings
- Script: 1) Bump out to visual studio with
- Proxies allow you to easily set up an API
- Redirection made easy
- Script: 1) Bump out to visual studio with
- Inner loop: a developers life day to day, writing and debugging code Outer loop: a developers life week to week, pushing code and monitoring their service We fulfill developer needs for both scenarios.
- Script: 1) Bump out to visual studio with
- “Why is monitoring important”
- Script: 1) Bump out to portal