Serverless Challenges

Serverless offering does provide unique opportunities such as pay-as-you-go model, event-driven architecture with auto-scale feature built-in, and abstraction of the infrastructure layer with a focus on business value. When you want to implement, there are 3 challenges: application rearchitecting, networking and security. This talk is about how to get around them.

Transcript

1. Serverless Challenges Unique Challenges with Unique Value Proposition Ebru Cucen • Contino
2. @ebrucucen 2 Agenda 01 | Why Serverless? 02 | Application Challenges 03 | Security Challenges 04 | Networking Challenges
3. @ebrucucen 3 Key Takeaways • Serverless provides the highest level of abstraction to enable focus on business value • As we shift away from non-differentiating infrastructure, old and new challenges at application level still need to be tackled • Azure is on the market offering some interesting features in the serverless space in comparison to AWS
4. @ebrucucen VEGAN PROUD WIFE PROUD MUM 4 CLOUD CONSULTANT @ebrucucen DEVELOPER AT HEART
5. Why Serverless?
6. @ebrucucen 6 Serverless Offering Simon Wardley “Serverless enables us, for the first time, to put a clear price tag on an application flow, allowing unprecedented visibility and accuracy when designing the supply chain of our businesses.”
7. @ebrucucen 7 https://martinfowler.com/articles/serverless.html Serverless Offering 01 Abstraction of infrastructure management 02 Pay-as-you-go 03 Auto-scale
8. @ebrucucen Focus on Your Application and Business Value 8 Data Center Networking Storage Servers Virtualisation Runtime Containers Applications Enterprise IT Functions Data Center Networking Storage Servers Virtualisation Runtime Containers Applications IaaS Functions Data Center Networking Storage Servers Virtualisation Runtime Containers Applications CaaS Functions Data Center Networking Storage Servers Virtualisation Runtime Containers Applications PaaS Functions Data Center Networking Storage Servers Virtualisation Runtime Containers Applications Serverless Functions Customer Vendor
9. Serverless Is Much More than Functions 9
10. @ebrucucen 10 Migrating More… Always-on option? But I heard it is expensive …
11. @ebrucucen 11 Migrating More… Always-on option? But I heard it is expensive …
12. @ebrucucen 1 concurrent exec for 1GB Resource Consumption: • 2.2m GBs/month • £950.4 Execution: • 1.6m GBs • £8.64/month Migrating More: Year Plan (WestEurope) 12 £959 https://www.slideshare.net/TimWagner/serverlessconf-2018-keynote-debunking-serverless-myths Standard_B2s: (2CPU/4GBRAM) £313/annual Linux VM £939
13. @ebrucucen 13 Is It Even? • High-Available: x more VMs • Load Balancer • Queue Storage • Management Costs
14. @ebrucucen 1 concurrent exec for 1GB Resource Consumption: • 2.2m GBs/month • £950.4 Execution: • 1.6m GBs • £8.64/month VM: £626 (2 Standard_B2s) LB: £240/year £866x3 = WINNER 14 £959 £2.598
15. Demo
16. Demo Gods: https://asciinema.org/a/bOH5uknb92QTLqHSDFtDxjMee
17. Application Challenges
18. Migration Patterns -> Strangler, Abstraction by Branch Application Level Challenges 18 Language Trade Offs -> Runtime, Triggers A B Debugging -> Logging, Monitoring, Tracing C Caching, Versioning -> API Manager D
19. Language Options • NET Core (Linux/Windows) • Node.JS (Linux/Windows) • Java (Windows) • Powershell Core (Windows) • Python (Linux) 19
20. @ebrucucen Triggers Input: • Http • Timer • Azure Storage • Azure Cosmos DB • Azure Service Bus • Azure Event Grid • Azure Event Hub • Azure IoT Hub 20 Output: • Http • Azure Storage • Excel • Azure Service Bus • Azure Event Hub • SendGrid • Twilio • Outlook Mail
21. Migration Patterns -> Strangler, Abstraction by Branch Application Level Challenges 21 Language Trade Offs -> Runtime, Triggers A B Debugging -> Logging, Monitoring, Tracing C Caching, Versioning -> API Manager D
22. @ebrucucen Postcode Lookup Service Migration 22 Microservice Verify Phone Register Customer Postcode Lookup
23. @ebrucucen Postcode Lookup Service Migration 23 Which Pattern First? Verify Phone Register Customer Postcode Lookup How to decouple/ migrate?
24. @ebrucucen Strangler Pattern 24 1. Identify Existing Call Postcode Lookup API
25. @ebrucucen Strangler Pattern 25 1. Identify Existing Call Postcode Lookup API 2. Move Existing Call Postcode Lookup API Refactor Before / after? New language ?
26. @ebrucucen 1. Identify Existing Call Postcode Lookup API Strangler Pattern 2. Move Existing Call Postcode Lookup API Redirected Call Lookup Function 3. Redirect Postcode Lookup API 26 Refactor Before / after? New language ? Leave/ Remove ?
27. @ebrucucen Postcode Lookup Service Migration 27 How to Connect? Verify Phone Register Customer Postcode Lookup Postcode Lookup
28. @ebrucucen 28 Branch by Abstraction Pattern User Registration Abstraction User Registration Implements
29. @ebrucucen 29 Branch by Abstraction Pattern User Registration Abstraction User Registration Phone Verification Postcode Lookup Implements
30. @ebrucucen 30 Branch by Abstraction Pattern User Registration Abstraction User Registration Phone Verification Postcode Lookup Implements
31. @ebrucucen 31 Branch by Abstraction Pattern User Registration Abstraction User Registration Implements Phone Verification Postcode Lookup
32. @ebrucucen User Registration Abstraction User Registration Phone Verification Postcode Lookup Implements 32 Branch by Abstraction Pattern User Registration Abstraction User Registration Implements Phone Verification Postcode Lookup User Registration Abstraction User Registration Phone Verification Postcode Lookup Implements
33. @ebrucucen 33 Postcode Lookup User Registration User Registration Abstraction New User Registration Service Phone Verification Postcode Lookup Implements Serverless Promise: #autoscales So do I need to think about autoscaling of overall system?
34. Serverless Design Patterns Address Lookup Address Verification Register User 34 Chaining
35. @ebrucucen Serverless Design Patterns 35 Onboard User Register User State Machine Email Verification Phone Verification Address Lookup
36. @ebrucucen 36 Azure Durable Functions Email Verification Phone Verification Address Verification Orchestrator Activity Functions Orchestrator Client WebApp
37. Migration Patterns -> Strangler, Abstraction by Branch Application Level Challenges 37 Language Trade Offs -> Runtime, Triggers A B Debugging -> Logging, Monitoring, Tracing C Caching, Versioning -> API Manager D
38. @ebrucucen 38 Starter Function
39. @ebrucucen 39 Orchestration Function
40. @ebrucucen 40 Activity Function
41. @ebrucucen Application Level Challenges 41 Language Options -> Runtime, Triggers Migration Patterns -> Strangler, Abstraction by Branch, Chaining, State Machine/Durable Functions Debugging -> Logging, Monitoring, Tracing Caching, Versioning -> API Manager A B C D
42. @ebrucucen Observability and Tracing • Debugging locally • Portal Kudo • Bash/shell into • Process Explorer • Live metrics 42
43. @ebrucucen Local Development 43
44. @ebrucucen Portal Logs 44
45. @ebrucucen Portal Kudo 45
46. @ebrucucen Process Explorer 46
47. @ebrucucen Application Map 47
48. Live Metrics 48
49. Dashboard 49
50. Language Trade Offs -> Runtime, Triggers Application Level Challenges 50 Migration Patterns -> Strangler, Abstraction by Branch A B Debugging -> Logging, Monitoring, Tracing C Caching, Versioning -> API Manager D
51. Serverless + API Manager = Epic Awesomeness 51
52. Shared Concerns: Security 52
53. How API Manager solves 53
54. Security Challenges
55. • Standards/Policies • Cloud Security Posture • Input sanitisation • Token validation for each function Drawbacks 55
56. Secure Http Endpoint: • Use API Management for auth • Use Authorization Keys Func Level • Integrate into Identity • Consider Rate throttling • Enable Cost Alerts Security - Top 5 recommendations 56
57. Networking Challenges
58. I need a Private Address! 58
59. I need on Prem Connection! 59
60. Unified APIs (each side) 60
61. API Manager 61
62. Network • Castle and moat approach* • Point-to-Point to integrations/Route Table • Communicate to back to on-prem? • Life before and after Private Links 62 https://www-microsoft-com.cdn.ampproject.org/c/s/www.microsoft.com/en-us/microsoft-365/blog/2019/09/18/why-banks-adopt-modern-cybersecurity-zero- trust-model/amp/
63. @ebrucucen 63 Key Takeaways • Serverless provides the highest level of abstraction to enable focus on business value • As we shift away from non-differentiating infrastructure, old and new challenges at application level still need to be tackled • Azure is on the market offering some interesting features in the serverless space in comparison to AWS
64. Reference 64
65. @ebrucucen References Serverless https://martinfowler.com/articles/serverless.html Serverless Myths: https://www.slideshare.net/TimWagner/serverlessconf-2018-keynote-debunking-serverless-myths Burning Monk Links: http://blog.binaris.com/your-guide-to-migrating-existing-microservices-to-serverless/ https://blog.binaris.com/how-to-go-all-in-with-serverless-adoption/ (All) https://medium.com/theburningmonk-com/all-my-posts-on-serverless-aws-lambda-43c17a147f91 65
66. @ebrucucen Books... 66
67. Atlanta atlanta@contino.io Questions contino.io continohq contino London london@contino.io New York newyork@contino.io Melbourne melbourne@contino.io Sydney sydney@contino.io
68. Atlanta atlanta@contino.io Thank you contino.io continohq contino London london@contino.io New York newyork@contino.io Melbourne melbourne@contino.io Sydney sydney@contino.io