Go Serverless: Design Patterns, Best Practices and Real-World Scenarios

Size: px

Start display at page:

Download "Go Serverless: Design Patterns, Best Practices and Real-World Scenarios"

Annice Thomas
5 years ago
Views:

2 Microsoft Tech Summit 2018 微软技术暨生态大会 Go Serverless: Design Patterns, Best Practices and Real-World Scenarios APP203 Davide Benvegnu Cloud Solution Architect

3 Cloud Solution Microsoft HK Former MVP for VSALM Former MMA fighter (6-1)

4 Agenda What is Serverless? Serverless on Azure Patterns Real-world examples Best practices

5 Serverless?

6 WHAT IS SERVERLESS?

7 WHAT ARE THE BENEFITS?

9 Serverless on Azure

10 Azure Serverless Ecosystem

11 Azure Functions Serverless Accelerate development Bind into services Bash Batch C# F# Java (v2) Javascript Php PowerShell Python </> Azure Service Bus Dropbox Azure Event Hub Sendgrid Azure Storage CosmosDb Event-driven scale Reduced Dev Ops Develop your way Local development OneDrive Box Twilio

solutions Visual workflow designer Event

Functions CosmosDb BizTalk Server Visual

12 Azure Logic Apps Connect anything Developer productivity Build holistic solutions Visual workflow designer Event based triggering Azure Service Bus Azure Event Hub Machine Learning IDE Support Looping control flow Cognitive Services Functions CosmosDb BizTalk Server Visual debug history Verbose Debugging Blob Storage HD Insight SQL Database

13 Serverless Patterns

14 Patterns Every 15 minutes Find and clean invalid data Clean table

15 Patterns CSV File added to Blob Storage Transform CSV to Data rows Power BI Chart graphic

16 Patterns Excel file saved to OneDrive Microsofr Graph API analyzes content Creates new sheets with charts

17 Patterns Loaded web page Calls WebHooks Create ad based on user profile Completed page

18 Patterns Photo taken and WebHook called Stores in blob storage Produces scaled images

19 Patterns Millions of devices feed into Stream Analytics Transform to Structured data Store data in SQL Azure

20 Patterns?... Message sent to Chatbot Cortana Analytics answers questions Chatbot sends response

21 Real world scenarios

22 Italian Red Cross Volunteer shifts managing application Shifts are published in the web app, at a specific, well-know time Volunteers access the web app and book their preferred shift(s) System works in a first-come-first-serve basis Needs to be always available Load on the system during peek time is huge Previous system in asp.net 1.1, vb.net, sql 2005, on-prem It was a Disaster

24 Italian Red Cress - Notes Functions in consumption mode scale perfectly CosmosDB w/autoscale can handle peak load Native integration with Functions rocks Functions for 3 rd party integration use Proxies and OpenAPI Just 2 WebApp instances can handle everything Specs Asp.net Core 2.0 (frontend) Functions use C# (compiled)

25 HK Shipping Company Company website revamped, wanted to revamp shipping tracking Single form to check shipping The system has to first understand what shipping type Then connect to the proper datasource They had no logs/metric of existing load (users, requests, etc) Good point for serveless as no idea of what to provision They want to have single shipping summary page Previously every shipping type had its own page Need to normalize data (DataSources & APIs return data in different formats) This is a job for Functions!

27 HK Shipping Company - Notes They didn t have capacity planning, with Serverless they didn t need it Both LogicApps and Functions in consumption mode scale as needed We use Application Insights so now they have usage logs and metrics Specs WebSite is in PHP (Wordpress) Functions are written in C# (1, for Oracle connection), Node.js

28 HK Shipping Company - Gotcha Sometimes the cold start slows down the overall process Application Insights still doesn t provide end-to-end monitoring Automatic dependencies tracking, etc It s on the RoadMap Need to be careful on handling the load on DBs / APIs And No cross-instance connection pooling

29 HK Shipping Company Serverless Futures Next part to go serverless will be the internal shipping tracking Data Insert into the different DataSources Data comes from cargos, terminals, agencies, etc Happy with LogicApps but may change to Durable Functions for complex orchestration (if needed)

30 Best Practices

31 Best Practices - Main Functions should do one thing Functions should finish as quickly as possible Functions should be stateless Functions should be idempotent

32 Best Practices Use Application Insights EVERYTIME Do as little work synchronously as possible Trigger in batches Don t forget to catch exceptions Global static variables for things like HttpClient or cached values Don t forget about the host.json file VSTS Release Management pipeline for DevOps Can also do GitHub / Source Control deploy for simple CI/CD

33 Best Practices - Security Standard PaaS / web app security is still a must-have New security tooling options needed More secrets, more secret management Permissions and grouping remember least privilege Mind both inputs and outputs the app is only as secure as its weakest link Networking solutions need development, but

34 Resources Azure Functions: Build apps faster and scale on demand (by Jeff Hollan)

35 Meet the Expert You are invited to further connect with this session s speaker at the foyer of the breakout room. Do not miss this opportunity to meet our expert!

36 Encourage and inspire the speaker for greater performance and submit your feedback for a chance to win a limited edition gift!

Industry-leading Application PaaS Platform

Industry-leading Application PaaS Platform Solutions Transactional Apps Digital Marketing LoB App Modernization Services Web Apps Web App for Containers API Apps Mobile Apps IDE Enterprise Integration