The document discusses Azure Functions, highlighting their serverless, event-driven nature and different programming languages supported. It emphasizes aspects such as cost efficiency, development processes, testing strategies, and platform limitations while mentioning various integration capabilities with Azure services. Additionally, the document outlines upcoming features and best practices for deploying and managing Azure Functions.

1. PUTTING THE ‘CTIONS’
IN AZURE FUNCTIONS
DEVELOP, BUILD, TEST, DEPLOY, REPEAT.

2. ‘SERVERLESS’
• Event driven
• Pay-per-use/per-trigger
• Scalable
• Not a golden hammer

3. AZURE FUNCTIONS
• C#, F#, Node.js, Python, PHP, Batch, Bash, PowerShell
• Trigger based
• Consumption plan
• $0.20 per million executions
• $0.000016 per GB of memory per second of execution
• App Service Plan

4. EXAMPLE SERVICE

5. EXAMPLE SERVICE

6. EXAMPLE SERVICE

7. EXAMPLE SERVICE

8. EXAMPLE SERVICE

9. EXAMPLE SERVICE

10. EXAMPLE SERVICE

11. EXAMPLE SERVICE

12. PORTAL EXPERIENCE – DEMO

13. PORTAL LIMITATIONS
• C# Scripting - .CSX
• Compile time issues
• Syntax errors
• Dependency issues
• Nuget restore issues
• Intellisense
• Testing
• Environment Promotion – Development/Staging/Production

14. WEBJOB SDK
• Azure Functions are built on of WebJobs
• Open source:
• https://github.com/Azure/azure-webjobs-sdk
• https://github.com/Azure/azure-webjobs-sdk-script
• Bindings & Triggers

15. VISUAL STUDIO 2017 - DEMO

16. Binding Attribute NuGet package
Blob storage trigger, input, output BlobAttribute, StorageAccountAttribute Microsoft.Azure.WebJobs
Cosmos DB input and output
binding DocumentDBAttribute Microsoft.Azure.WebJobs.Extensions.DocumentDB
Event Hubs trigger and output EventHubTriggerAttribute, EventHubAttribute Microsoft.Azure.WebJobs.ServiceBus
External file input and output ApiHubFileAttribute Microsoft.Azure.WebJobs.Extensions.ApiHub
HTTP and webhook trigger HttpTriggerAttribute Microsoft.Azure.WebJobs.Extensions.Http
Mobile Apps input and output MobileTableAttribute Microsoft.Azure.WebJobs.Extensions.MobileApps
Notification Hubs output NotificationHubAttribute Microsoft.Azure.WebJobs.Extensions.NotificationHubs
Queue storage trigger and output QueueAttribute, StorageAccountAttribute Microsoft.Azure.WebJobs
SendGrid output SendGridAttribute Microsoft.Azure.WebJobs.Extensions.SendGrid
Service Bus trigger and output ServiceBusAttribute, ServiceBusAccountAttribute Microsoft.Azure.WebJobs.ServiceBus
Table storage input and output TableAttribute, StorageAccountAttribute Microsoft.Azure.WebJobs
Timer trigger TimerTriggerAttribute Microsoft.Azure.WebJobs.Extensions
Twilio output TwilioSmsAttribute Microsoft.Azure.WebJobs.Extensions.Twilio
TRIGGERS/BINDINGS
https://docs.microsoft.com/en-us/azure/azure-functions/functions-dotnet-class-library

17. SERVICE DESIGN*
• Functions class library as ‘glue’
• Standard service design
• Service ideally shouldn’t know about functions
• Functions shouldn’t know about your service’s requirement
*Purely things that have worked for me

18. TESTING
• Test your services as services
• Functions CLI – Test locally
• Consumption plan is cheap/free!

19. BUILDING
• Just like a normal build pipeline
• Bamboo/Jenkins/VSTS
• Use build output
• Known bug when using local file system publish

20. DEPLOYING - DEMO

21. WHAT’S NEW
• Function Slots
• Only allowed 1
• Function Proxies
• Event Grid – “Serverless” EventHub

22. WHAT’S COMING
• BYOB – Bring you own bindings
• Method Dependency Injection
• Custom bindings
• Durable Functions
• Durable Task Framework on Functions
• Easy orchestration of persistent workflows using async/await
• .NET Core Support

23. WHAT TO LOOK OUT FOR
• Emulating locally?
• Start the Azure storage emulator
• “UseDevelopmentStorage=true”
• [Singleton] attribute isn’t available in Functions
• Does you function have a [FunctionName]?
• Big functions!
• Keep them tiny 

24. QUESTIONS?