This slide deck provides the basics of how you can build Nano Services using Azure Functions. This presentation was presented by Sunny Sharma, Senior Software Engineer at BizTalk360 and a Microsoft MVP during the TechMeet360 event organized by BizTalk360, held on December 17, 2016 at Coimbatore.

1. Sponsored & Brought to you by
Learn Building Nano Services
using Azure Functions
Sunny Sharma
Microsoft MVP
https://www.linkedin.com/in/sunny-sharma-8725031a
https://twitter.com/Sunny_Delhi

2. • SSE @ BizTalk360
• Microsoft MVP, C# Corner MVP
• twitter: @sunny_delhi
• fb: bit.ly/sunnykumar
<About Me/>
Codeflair.net

3. What we are going to discuss?
 Azure Functions Fundamentals
 Azure Functions Architecture
 Demo - Building Nano Services
 Q&A

4. What is Azure Functions?

5. Azure Functions

6. Azure Functions - Features
 Serverless Architecture
 Modularity & Flexibility
 Event-based
 Easily Integrated into workflows
 Scalability
 Full .NET Core support

7. Language Support
C# F# Node.js
Python PHP Batch
Bash Any other Executable

8. • Languages and Framework
• Superior DevOps
• Self served
• Something else
Apps
Web Apps Mobile Apps API Apps Functions
eCommerce Digital Global Presence LOB API / Services / ISVCustom Apps
App Service
• Limitless/Auto
• OS and Framework
• Load balance
• Something else
• Enterprise grade SLA
• Secure and Compliance
• On-Premise Connectivity
• Something else

9. 9
Azure Functions architecture
Built on top of App Service and WebJobs SDK

10. Supported bindings
Type Service Trigger Input Output
Schedule Azure Functions ✔
HTTP (REST or WebHook) Azure Functions ✔ ✔
Blob Storage Azure Storage ✔ ✔ ✔
Queues Azure Storage ✔ ✔
Ques and Topics Azure Service Bus ✔ ✔
Tables Azure Storage ✔ ✔
Tables Azure Mobile Apps ✔ ✔
No-SQL DB Azure DocumentDB ✔ ✔
Streams Azure Event Hubs ✔ ✔
Push Notifications Azure Notification Hubs ✔
Twilio SMS Text Twilio ✔

11. Azure WebJobs Azure Functions
 Need to managed on Azure WebApps
 Supports Continuous / Triggered process
 Works with Azure App Service Plan
 Scaling is manual
 Can be developed / debugged using Visual
Studio
 Less Turn Around Time compared to Azure
Functions
 Serverless – No Management needed
 Can be triggered only
 Azure App Service Plan / Dynamic App
Service plan
 Auto Scales on requests
 Can be developed / debugged using Visual
Studio
 Less Turn Around Time compared to Azure
Functions

12. Azure Functions - Composition
 Run file: contains all the code
 Function file: contains service bindings / triggers /
parameters
 Project file: contains project assembly and NuGet Package
references
 Configuration: Connection strings and API keys

14. Demo time

15. Debug Azure Functions in Visual Studio
https://aka.ms/azfunctiontools
Download Microsoft Azure App Service Tools

16. Platform and Scaling
App Service offers two pricing tiers.
App Service / Dedicated Tier Dynamic Tier
• Basic / Standard / Premium
• Pay based on # of reserved
VMs
• You’re responsible for scaling
• Pay on number of executions
• Platform is responsible for
scaling

18. bit.ly/
AzureFuncFeedback
I Feedback!

19. References
https://functions.azure.com
https://tryappservice.azure.com

20. Thank You!

twitter: @sunny_delhi
Sunny.Sharma@BizTalk360.co.uk

21. Get in touch with us …
facebook.com/BizTalk360
twitter.com/BizTalk360
plus.google.com/+Biztalk360
instagram.com/BizTalk360
linkedin.com/company/biztalk3
60
youtube.com/user/biztalk360
Twitter & Facebook Hashtag - #techmeet360