1. ABC of Azure Functions
Samik Roy
Senior Developer
Born In The Cloud
@roy_Samik
https://www.linkedin.com/in/roysamik/
samik.n.roy@gmail.com
2. Agenda
• Why Azure Functions
• Plans to choose
• The Demo followed by Q&A
3. The Story
1. Requires an infrastructure
2. Requires all dependencies
to be installed in the
machine.
3. Machine is billed even in
idle time.
1. Requires no infrastructure.
2. Developer can focus on only
logic so time to market is
fast.
3. Very cheap option compare
to VMs.
4. Auto scale up options
available.
5. How Azure Function is executed !
Function
triggers
based on
event
Compute an
d storage
resources
allocated
Execution of
logic
Deallocation
of resources
7. Plans to choose
Azure function has 2 types of plans
Consumption Plan
1. Pay only when your functions are running.
2. Scale out automatically, even during periods of high load.
App Service Plan
1. You have existing, underutilized VMs that are already running other App Service instances. You
expect your function apps to run continuously, or nearly continuously. In this case, an App
Service Plan can be more cost-effective.
2. You need more CPU or memory options than what is provided on the Consumption plan.
3. You need to run longer than the maximum execution time allowed on the Consumption plan (of
10 minutes).
4. You require features that are only available on an App Service plan, such as support for App
Service Environment, VNET/VPN connectivity, and larger VM sizes.
5. You want to run your function app on Linux, or you want to provide a custom image on which to
run your functions