This document provides an overview of Azure Functions and serverless computing. It begins with welcoming attendees and thanking sponsors. It then introduces the presenter and their background. The document defines Azure Functions and serverless computing, outlines their benefits, and describes key concepts like triggers, bindings, and application components. It compares Azure Functions v1 and v2 and provides a demo. It also discusses where Functions fit and lists some open source Microsoft products.

1. Welcome to the
Chandigarh@codestellar

2. A BIG thank you to the 2019 Global Sponsors!
@codestellar

3. Another BIG thank you to local sponsors!
@codestellar

4. Gaurav Madaan
(Principal Consultant at Technossus)

5. Who am I?
• Principal Consultant at Technossus
• 7+ years of experience in IT
• MCSD, App Builder
• Open Teacher
• SAFe 4 Practitioner
@codestellar

7. What are Azure Functions?
Execute your code in response to any event
@codestellar

8. Event-driven
scale
Micro-second
billing
Abstraction
of servers
What is Serverless?
@codestellar

9. Benefits of ‘SERVERLESS’
Manage less
Micro-pricing
Ease of scale
@codestellar

10. Key Concepts
• Function App: Unit of development,
deployment and scaling. Can have
many functions.
• Triggers: Event Source that invokes
the function. One per function.
• Bindings:
• Input: Data that is pulled in at the
start of execution. Can be
multiple.
• Output: Data that is pushed out
after the execution. Can be
multiple.
https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings

11. Serverless Application Platform Components
@codestellar

12. Consumption Plan
New Premium Plan
(Preview)
Instance Size
Fixed at 1 core and 1.5 GB of
memory
Configurable up to 4 cores and 14
GB of memory
Scaling Event Driven Scaling Event Driven Scaling
Scale Controls None Set min and max instances
Private
Networking
None VNET Integration
Warmup Time
(Cold Start)
Your app must be loaded after it is
inactive
No delay after your app is inactive
and scale instantly to pre-warmed
instanced
Cost Consumption
Consumption and at least 1 pre-
warmed instance

13. Azure Functions v1 vs v2
• Keys for calling function endpoints are stored in blob storage in V2.
Earlier it was file storage by default
• All functions in a function must have same language (Runtime stack)
• You can set maxConcurrentRequests. Default 100
• For better monitoring, APPINSIGHTS_INSTRUMENTATIONKEY is used.
• https://docs.microsoft.com/en-us/azure/azure-functions/functions-
versions
@codestellar

14. Who wants a goodie?
In how many regions, Azure is generally available?
Azure is generally available in 44 regions around the world, with plans announced for 10 additional regions.
https://azure.microsoft.com/en-us/global-infrastructure/regions/
@codestellar

15. May the DEMO Gods be with Us!May the DEMO Gods be with Us!May the DEMO Gods be with Us!
@codestellar

17. Where Functions Fit?
Processing on top of
event streams (IoT,
Event Hubs)
Web API(s) and Mobile
Backends
Glue between Systems
Automating Scripts and
Jobs
Pub/Sub Patterns

22. Who wants a goodie?
Name three open source products by Microsoft?
VSCode, .Net Framework, Calculator
@codestellar

23. Final
Thoughts!
Try Azure Functions
https://azure.microsoft.com/en-
in/pricing/details/functions/
https://github.com/Azure/Azure-
Functions/wiki/Samples-and-
content