Azure Functions

AZURE
FUNCTIONS
CLOUDIFICATION

WHAT TO EXPECT :
2
GET FAMILIAR WITH AZURE FUNCTIONS
PRICING MODEL
DEMO
MANAGEMENT, SECURITY AND PERFORMANCE
Copyright © 2017 AxEdge Consulting. All rights reserved.

3
AZURE FUNCTIONS
 Azure Functions is a serverless compute
service that enables you to run code on-
demand without having to explicitly provision or
manage infrastructure
 Functions provides a fully managed
compute platform with high reliability and
security.
• Manage your apps instead of infrastructure.
• Gain flexible scaling.
• Only pay for resources you use.

AZURE FUNCTIONS - FEATURES
Easily leverage Azure services and
software-as-a-service (SaaS)
offerings.
Pay only for the time spent
running your code depending
on
• Executions.
• Resource Consumption
Write functions using:
C#, F#, Node.js, Python, PHP,
batch, bash, or any executable.
• Protect HTTP-triggered functions with
OAuth provider.
• Managed Service Identity.
• RBAC
• Supports NuGet and NPM
CHOICE OF LANGUAGE SECURITY
SIMPLIFIED INTEGRATION PRICING
4
BRING YOU DEPENDENCIES
FLEXIBLE DEPLOYMENT
• Through Azure Portal.
• Set up continuous
integration and deploy your
code through
 GitHub
 Visual Studio Team
Services

AZURE FUNCTIONS ARCHITECTURE
Built on top of App Service and Webjobs SDK

SUPPORTED LANGUAGES
Copyright © 2017 AxEdge Consulting. All rights reserved. 6

Microsoft Confidential
TRIGGERS
7
 A trigger defines how a function is
invoked.
 A function must have exactly one trigger.
 Triggers have associated data, which is
usually the payload that triggered the
function.
 Direction of a trigger is always in.

INTEGRATIONS – OUTPUT/ INPUT BINDINGS
COSMOS DB
AZURE SERVICE BUS
GITHUB
NOTIFICATION HUB
AZURE STORAGE
AZURE EVENT HUB
AZURE MOBILE TABLETS

SUPPORTED BINDINGS
TYPE SERVICE TRIGGER INPUT OUTPUT
Schedule Azure Functions ✔
HTTP (REST or webhook) Azure Functions ✔ ✔**
Blob Storage Azure Storage ✔ ✔ ✔
Events Azure Event Hubs ✔ ✔
Queues Azure Storage ✔ ✔
Queues and topics Azure Service Bus ✔ ✔
Storage tables Azure Storage ✔ ✔
SQL tables Azure Mobile Apps ✔ ✔
NoSQL DB Azure Cosmos DB ✔ ✔ ✔
Push Notifications Azure Notification Hubs ✔
Twilio SMS Text Twilio ✔
SendGrid email SendGrid ✔
Excel tables Microsoft Graph ✔ ✔
OneDrive files Microsoft Graph ✔ ✔
Outlook email Microsoft Graph ✔
Microsoft Graph events Microsoft Graph ✔ ✔ ✔
Auth tokens Microsoft Graph ✔

AZURE FUNCTIONS
TECHNICAL CONCEPTS AND COMPONENTS
FUNCTION APP
 Comprised of one or more
individual functions that are
managed together by azure app
service.
 All of the functions in a function
app share the same pricing plan,
continuous deployment and
runtime version.
RUNTIME
The runtime, or script host, is the
underlying webjobs SDK host
that
• listens for events
• gathers and sends data
• ultimately runs your code
To facilitate http triggers, there is
also a web host that is designed
to sit in front of the script host in
production scenarios.
Having two hosts helps to isolate
the script host from the front end
traffic managed by the web host
FUNCTION CODE
 A function is the primary concept
in Azure Functions.
• Write Code in a Language of
your choice.
• Save the code and configuration
files in the same folder.

CONSUMPTION PLAN
Consumption plan – Pay as you go.
• Dynamic scaling based on the number of incoming requests.
• Pricing based on Resource consumption and Executions.
• Free grant of 1 million requests and 400000 GBs.
• Maximum execution time of 10 mins for a function.
• Max memory limit of 1.5 GB per instance of function host.

APP SERVICE PLAN
App Service plan
• Function apps run on dedicated VMs on Basic, Standard, Premium, and Isolated SKUs.
• Azure function host is always running.
• Same as cost of VMs.
• Scale out using autoscaling.
Consider an App Service plan in the following cases:
 Existing, underutilized VMs that are already running other App Service instances.
 Function apps to run continuously, or nearly continuously.
 More CPU or memory .
 Run functions longer than the maximum execution time allowed on the Consumption plan (of 10 minutes).
 Require features that are only available on an App Service plan.

PERFORMANCE CONSIDERATIONS
Avoid Long Running Functions
Functions should be stateless
and idempotent if possible.
Cross function communication
Write defensive functions
Use async code but avoid
blocking calls
Don't mix test and production
code in the same function app

SECURITY FEATURES
 Azure services integration is done with TLS encrypted connections (over port 443).
 Supports SSO.
 Integrated with managed service identity
 Can be integrated with azure active directory (AAD)
 Supports on premise secure token service (STS) such as active directory federation
services (adfs).
 Supports popular authentication protocols, such as oauth 2.0, openid connect, and SAML
2.0
 Can also configure function apps to use 3rd party login authentications like Facebook,
Google, Microsoft account and Twitter.

MONITOR
Application Insights for monitoring functions.
 You can use application insights without any custom configuration, but
the default configuration can result in high volumes of data and can hit
data cap for app insights.
Azure functions logger includes:
Categories
 The category indicates which part of the runtime code or your function
code wrote the log.
Log levels
 The azure functions logger also includes a log level with every log
Real-time monitoring
Monitor log files from a command line
Monitor function app log files with PowerShell

DURABLE FUNCTIONS
FUNCTION CHAINING FAN-OUT/FAN-IN ASYNC HTTP APIS
STATEFUL SINGLETONS HUMAN INTERACTION

Azure Functions

More Related Content

What's hot (18)

Similar to Azure Functions (20)

Recently uploaded (20)

Azure Functions