1. Using Azure Functions to Build Nanoservices
Microsoft Virtual Academy
Header
Using Azure Functions to Build Nanoservices
Scott J. Peterson
Produced by

2. Azure Function Apps
Create a “serverless” event driven experience that extends the existing Azure App Service platform, by building “nanoservices” that can scale based on demand.

3. Supported Languages & Tools
Create functions in JavaScript, C#, Python, and PHP, as well as scripting options such as Bash, Batch, and PowerShell, that can be triggered by virtually any event in Azure, 3rd party services, or on premise systems.

4. The Agenda Common Scenarios The Azure Function App Environment
Function App Templates
Timer Function Apps
Data Processing Function Apps
Webhook & API Function Apps
Advanced Scenarios
Next Steps
Tips & Tricks

5. Common Scenarios Timer-based processing Azure service event processing
SaaS event processing
Serverless web application architectures
Serverless mobile backends
Real-time stream processing
Real-time bot messaging
Your App or Service
Office 365
Office Graph
Azure Storage
Other Functions
Legacy Systems
Web Services

6. The Azure Function App Environment
Function Apps are part of the new “Web + Mobile” Suite
Function App management is not available via the “Classic” Azure Portal
Create and manage Functions directly via the Azure Function App Designer at:
Integrate Functions into your ecosystem via the Azure Portal at:
Creation, management, and configuration tool are (in general) web based

7. The Azure Function App Environment

8. Function App Templates
Function App templates are categorized into general areas of Timer, Data Processing, and Webhook & API.
BlobTrigger
EventHubTrigger
Generic webhook
GitHub webhook
HTTPTrigger
QueueTrigger
ServiceBusQueueTrigger
ServiceBusTopicTrigger
TimerTrigger
Blank & Experimental

9. Function App Templates

10. Timer Function Apps
Run at explicitly specified intervals, like every day at 2:00 am using CRON expressions, like “0 */5 * * * *“ (every 5 minutes)
Can send information to other systems, but typically don’t “return” information, only write to logs
Great for redundant cleanup and data management
Great for checking state of services
Can be combined with other functions

11. Timer Function Apps

12. Data Processing Function Apps
Run when triggered by a data event, such as an item being added to a queue or container
Typically have in and out parameters
Great for responding to CRUD events
Great for performing CRUD events
Great for moving content
Access data across services

13. Data Processing Function Apps

14. Webhook & API Function Apps
Triggered by events in other services, like GitHub, Team Foundation Services, Office 365, OneDrive, Microsoft PowerApps
Takes in a request and sends back a response
Often mimic Web API and legacy web services flows
Typically need CORS settings managed
Best for exposing functionality to other apps and services
Great for building Logic Apps

15. Webhook & API Function Apps

16. Advanced Scenarios Calling your function programmatically
Serializing and deserializing JSON data
Using 3rd party libraries via NuGet packages
Sending push notifications, i.e.; Toast, Tile and Raw payloads
Connecting a function to a Logic App

17. Advanced Scenarios

18. Next Steps Start migrating existing processes to Azure Functions
Identify 3rd party products to integrate via NuGet packages
Experiment with complex types, such as SQL Server geospatial data
Evaluate your Azure Resource and Storage configurations
Start working with Logic Apps, especially in areas of Office 365 integration

19. Using Azure Functions to Build Nanoservices
Scott J. Peterson, MCSD, MCPSB, MCT
Senior Enterprise Architect & Developer

20. Tips & Tricks
The new Azure Portal seems to respond better when using Firefox. Internet Explorer seems to respond better than Edge.
Store credentials, connection strings, and even authorization tokens in the Function App > Application Settings > App Settings or Connection Strings
If you delete and re-create a Function with the same name, it may populate the template with old, cached content. Try and rename Functions on create.
Get familiar with CRON expression syntax.
Good over:
Good example and builder: