Yochay Kiriaty gave a presentation on serverless computing using Microsoft Azure services. He began by defining serverless and its benefits like event-driven scaling, sub-second billing, and abstraction of servers. He then demonstrated several serverless patterns using Azure Functions for tasks like processing data from Blob storage, responding to API requests, and replicating logs between data centers. Throughout the presentation, he emphasized best practices for building serverless applications including designing functions to do single tasks, finish quickly, be stateless and idempotent.

2. Yochay Kiriaty
Principal Program Manager @ Microsoft
Azure / App Service
Tech Evangelist
Various Start Ups
https://blogs.msdn.microsoft.com/appserviceteam
@yochayk
yochay@microsoft.com

3. Agenda
• Why Serverless?
• Serverless patterns / Real-world examples

4. Event-driven/
instant scale
Sub-second
billing
Abstraction
of servers
What is Serverless?

5. Focus on
Business
Logic
Reduced Time
To Market
Reduced
DevOps
Benefits of Serverless?

6. CSV
? 
So many options, where do I start?

7. Microsoft Serverless Services
Cortana
Management Suite
Media ServicesStorage
Traffic
Manager
Visual Studio
Services
OMS
Management SuitMachine LearningCDNDocument DB
Search
SchedulerActive Directory Key Vault App Insights Cognitive Services Embedded Power BI
Hockey AppStream AnalyticsNotification HubIoT Hub Service Bus
Functions Logic App

8. Functions Programming Model
Trigger
(data)
Input Input
code
Output
Output
Input
Yochay to update to node.js
example

9. Serverless
Patterns

10. File added to
Blob Storage
Transform CSV to data rows Power BI
Chart graphic

11. Tasks/ Activities
 Protect against API DDOS
 Dynamically configure
CloudFlare (Block IP)
Source: https://www.troyhunt.com/azure-functions-in-practice/

12. Q msg
IP 2 block
DDOS
Site
Source: https://www.troyhunt.com/azure-functions-in-practice/

13. Tasks/ Activities
 Protect against API DDOS
 Dynamically configure
CloudFlare (Block IP)
Source: https://www.troyhunt.com/azure-functions-in-practice/
Before Serverless
Setup a VM/ Container/
WebJobs
Build/ patch/ deploy (OS)
Monitor infra (VM/
Container)
Use Azure SDK
Manage CloudFlare creds
Use CLoudFlare API
Using Serverless
Setup a VM/ Container/
WebJobs
Build/ patch/ deploy (OS)
Monitor infra (VM/
Container)
Use Azure SDK
Manage CloudFlare creds
Use CLoudFlare API

14. Functions Programming Model - Best Practices
• Functions should “do one thing”
1

15. Every 15 minutes Clean tableFind and clean invalid data

16. Tasks/ Activities
Replicate logs from one data
center to another
Analyze the logs
Take action based on data

18. Before Serverless
Setup a VM/ Container/
WebJobs
Build/ patch/ deploy (OS)
Monitor infra (VM/
Container)
Manage FTP creds
Use FTP library
Use Azure SDK
Tasks/ Activities
Replicate logs from one data
center to another
Analyze the logs
Take action based on data
Using Serverless
Setup a VM/ Container/
WebJobs
Build/ patch/ deploy (OS)
Monitor infra (VM/
Container)
Manage FTP creds, but with
automation with dynamic
settings
Use FTP library
Use Azure SDK

20. Blob Replication
Abnormal
behavior
FTP Download
Manager Function
Single Folder Single Folder Single Folder

21. Functions Programming Model - Best Practices
• Functions should finish as quickly as possible

22. Millions of devices feed
into Stream Analytics
Store data in
SQL Online
Transform to structured data

23. Tasks/ Activities
Collect tweets
Analyze tweets
Display rich analysis

24. Collect
Tweets
Logic
App
Analyze
Tweets
Store
Data
Store
Data

25. Tasks/ Activities
Collect tweets
Analyze tweets
Display rich analysis
Before Serverless
Setup a VM/ Container/
WebJobs
Build/ patch/ deploy (OS)
Monitor infra
Connect (auth)to twitter
Using Twitter API (SDK)
Analyze tweets
Build rich client to show results
Using Serverless
Setup a VM/ Container/
WebJobs
Build/ patch/ deploy (OS)
Monitor infra
Connect (auth)to twitter
Using Twitter API (SDK)
Analyze tweets
Build rich client to show results

26. Functions Programming Model - Best Practices
• Functions should be stateless
• Functions should be idempotent

27. Using digital insights to
optimize transactions in
the real world
Plexure

29. EVENT SWARM ENGAGEMENT CHANNELS
FLEXIBLE BIG DATA PIPELINE
INTELLIGENCE PIPELINE
3RD PARTY
EVENT INGESTION
ENGINE
SQL DATA
WAREHOUSE
DATA LAKE STORAGE
& ANALYTICS
STREAM
ANALYTICS
WEB
CUSTOM
SERVICES
WEARABLES
POS
DIGITAL
DISPLAYS
BOTS
KIOSKS
MOBILE APP
SENSORS
OMNI CHANNEL ENGAGEMENT
WORKFLOW
ORCHESTRATION
ENTERPRISE INTEGRATION
CUSTOM INTELLIGENCE
INTELLIGENT
SERVICES
CUSTOM
FUNCTIONS
MACHINE
LEARNING
COGNITIVE
SERVICES
EXISTING
NEW
API GATEWAY
API GATEWAY

30. Event-driven/
instant scale
Sub-second
billing
Abstraction
of servers
What is Serverless?

31. Functions Programming Model - Best Practices
• Functions should “do one thing”
• Functions should finish as quickly as possible
• Functions should be stateless
• Functions should be idempotent
1

32. Building Serverless Apps With Azure Functions
Instead of …
• pulling –> triggers
• ‘SDK’ –> bindings
• routes in a Web App (server) –> single function
• writing large functional tests against a server –> functional tests look
more like unit tests per function.
• building and deploying servers –> deploy collections of Functions

33. • Thick clients & stateless backends
• Statless  Scale
• SPA (Angular /React) are your friend (enable CORS )
• Sync works, but Async rocks!
• Async  Scale
• Async, queue based systems are more resilient
• Read and internalize the reactive manifesto - http://www.reactivemanifesto.org/
• Live and die by the cloud
• Develop on the cloud, test on the cloud, ship on the cloud
• Lots of different services
• Not just FaaS, but use other serverless tech that best solves the problem (like
Logic Apps)
Serverless Architecture- Best Practices

34. Microsoft and Serverless
Try Functions – https://functions.azure.com
Try App Service – https://tryappservice.azure.com