30. Tasks/ Activities
• Upload data to
storage
• Process data
• Expose REST API
Using Functions
• Setup a VM/
Container/ WebJobs
• Build/ patch/ deploy
• Monitor infra
• Build Web API App
• ‘Use Azure SDK’
• Built async data
processing (scale)
Before Functions
• Setup a VM/
Container/ WebJobs
• Build/ patch/ deploy
• Monitor infra
• Build Web API App
• Use Azure SDK
• Built async data
processing (scale)
Photo taken and
WebHook called
35. 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
36.
37. Tasks/ Activities
• Collect tweets
• Analyze tweets
• Display rich analysis
Using Serverless
• Setup a VM/
Container/ WebJobs
• Build/ patch/ deploy
• Monitor infra
• Connect (auth)to
twitter
• Using Twitter API
(SDK)
• Analyze tweets
• Build rich client to
show results
Before Serverless
• Setup a VM/
Container/ WebJobs
• Build/ patch/ deploy
• Monitor infra
• Connect (auth)to
twitter
• Using Twitter API
(SDK)
• Analyze tweets
• Build rich client to
show results
52. TriggerFunc F1 F2 F3
• Azure Queues (SNS/ SQS) are an implementation detail.
• Each individual Function needs to be “aware” of other functions.
• Functions need to be idempotent.
• Functions need to “DoWork” and “UndoWork”
53. TriggerFunc F1 F2 F3
• Azure Queues (SNS/ SQS) are an implementation detail
• Central Error Handling Function “understand” the chain/flow
Error Handler