Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 27

Microsoft Azure

Azure Functions

Bryan Rodríguez
Software Engineer
3
eCommerce Digital Global Presence Custom Apps LOB API / Services / ISV
Apps
Logic
APIM Mobile Apps
Apps

Notification Azure
API Apps Hubs Web Apps Functions
Services

App Service
Fully Managed Platform Enterprise Grade
Developer Experience
• Auto scale • Languages and Frameworks • Enterprise grade SLA
• OS and Framework patching • Superior DevOps • Security and Compliance
• Load balancing • Self service supportability • On-Premise Connectivity

Platform
Azure
Functions

Azure Functions
Code Azure Functions Events + data
Process events with Serverless code.

Make composing Cloud Apps insanely easy


Develop Functions in C#, Node.js, F#, Python, PHP, Batch and more
Easily schedule event-driven tasks across services
Expose Functions as HTTP API endpoints
Scale Functions based on customer demand
Easily integrate with Logic Apps
INTEGRATION DAY
MICROSOFT GTSC, Bengaluru September 10, 2016

Azure Functions architecture


Built on top of App Service and WebJobs SDK

Code Config

• Language Runtime
C#, Node.js, F#, PHP, etc.
WebJobs Script Runtime
Azure Functions Host – Dynamic Compilation, Language abstractions, etc.

WebJobs Core WebJobs Extensions


Programming model, common abstractions Triggers, input and output bindings

App Service Dynamic Runtime


Hosting, CI, Deployment Slots, Remote Debugging, etc.

7
INTEGRATION DAY
MICROSOFT GTSC, Bengaluru September 10, 2016

Platform and scaling


• App Service offers dedicated and dynamic tiers.
• Dedicated is the existing App Service plan tiers
• Basic, Standard, Premium
• Pay based on # of reserved VMs
• You’re responsible for scale
• Dynamic
• Pay on number of executions
• Platform responsible for scale

10
INTEGRATION DAY
MICROSOFT GTSC, Bengaluru September 10, 2016

What is the “Functions” programming model?


• Function as the unit of work
• Functions are executed; they start and finish
• Functions have inputs and outputs

11
INTEGRATION DAY
MICROSOFT GTSC, Bengaluru September 10, 2016

Best practices for the “Functions” model


• Functions should “do one thing”
• Functions should be idempotent
• Functions should finish as quickly as possible

1
12
INTEGRATION DAY
MICROSOFT GTSC, Bengaluru September 10, 2016

Functions programming concepts


Trigger Input

Code Output
13
Ejemplo

14

You might also like