Azure Functions allow developers to write code that runs in response to events, enabling event-driven architectures. Functions can be triggered by common data sources and services and support multiple programming languages. Functions provide automatic scaling and only run code when triggered, avoiding the need to manage servers. They integrate with other Azure services and can be developed, tested, and deployed using common tools like Visual Studio.

1. Azure Functions: What they are and
why they’re cool
Martin Abbott
@martinabbott

2. What are Azure Functions?
Code Events + dataAzure Functions

3. Getting things started

4. Azure Functions
code outputinput

5. Supported bindings
Type Service Trigger Input Output
Schedule Azure Functions ✔
HTTP (REST or WebHook) Azure Functions ✔ ✔
Blob Storage Azure Storage ✔ ✔ ✔
Queues Azure Storage ✔ ✔
Tables Azure Storage ✔ ✔
Tables Azure Mobile Apps Easy Tables ✔ ✔
No-SQL DB Azure DocumentDB ✔ ✔
Streams Azure Event Hubs ✔ ✔
Queue Azure Service Bus ✔ ✔
Topic Azure Service Bus ✔ ✔
Push Notifications Azure Notification Hubs ✔

6. Taking things further

7. Supported Languages
• 1st class support
• Node/JavaScript
• C#
• Experimental support
• F#
• Python
• PHP
• Batch
• Bash
• PowerShell

8. Building
• Development
• #r == reference
• #load == include
• Standard packages
• Nuget package restore
• Tools
• Visual Studio
• Remote debugging
• Visual Studio Monaco
• Kudu

9. Finishing things off

10. Built within App Service
• Runs on existing App Hosting
plans
• Run alongside Web, Mobile, and
API Apps
• Deploy via existing App Service
ARM APIs
• All the features of App Service
• Continuous Deployment
• Deployment Slots
• Authentication
• Run in your own isolated and
dedicated environment
• App Service Environment runs a
dedicated App Service
• Run inside of your own VNET, with
your own frontend and firewall

11. Scale an App Service
• Scale up to a larger VM for
more resources
• Scaling out as simple as a
slider bar
• Set up auto-scaling rules to
handle additional load
automagically

12. Lifting the covers

13. Built to scale

14. Servers when you want them…

15. Without dynamic compute

16. With dynamic compute

17. With dynamic compute at scale

18. Serverless when you don’t…

19. Why they’re cool
• Easy to create, test and change
• Options for development
• Visual Studio / Code / Online
• Kudu
• Package restore
• Shared code
• Event driven architecture
• Event chaining
• Event fan out
• Microservices
• Eventual consistency
• Internet of Things

20. More information
• Azure Functions
documentation
https://azure.microsoft.com/en-
us/documentation/services/functions/
• Azure Functions pricing
https://azure.microsoft.com/en-
us/pricing/details/functions/
• Azure Functions developer
reference
https://azure.microsoft.com/en-
us/documentation/articles/functions-
reference/