Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Serverless Pitfalls

68 Aufrufe

Veröffentlicht am

What is serverless? Its benefits and challenges.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Serverless Pitfalls

  1. 1. Serverless Pitfalls Kate Semizhon
  2. 2. Kate Semizhon Engineering Manager ● Epam Systems / Sephora / Radius Intelligence Joining Square next week Expecting a baby-boy 👶 in November @anaris_s
  3. 3. What is Serverless (FaaS) is an execution model where the cloud provider is responsible for executing a piece of code by dynamically allocating the resources.
  4. 4. Road to Serverless
  5. 5. Server-side Host Application Operation Operation Serverless Operation Operation Serverless
  6. 6. Where it’s available AWS Lambda Microsoft Azure Functions Google Cloud Functions
  7. 7. Use Case #1
  8. 8. Use Case #2
  9. 9. Benefits
  10. 10. Cost Savings ● Don’t need to keep servers up when we are not serving out any requests ● Reduced labor cost
  11. 11. Time Savings ● On maintenance ● On applying the appropriate security updates to the server
  12. 12. Scaling ● Scales up and down behind the scene
  13. 13. Pitfalls
  14. 14. How to setup a source control for serverless: ● to share code ● do not inflate distribution artifact
  15. 15. Code Management Multi-repoMono-repo vs
  16. 16. Mono-Repo Code sharing between functions No need to support multiple repositories and deployment processes
  17. 17. Mono-Repo Code sharing between functions No need to support multiple repositories and deployment processes Cloud provider might have a restriction on size of the artifact
  18. 18. Mono-Repo Disadvantages Size of an artifact Solution: artifact per lambda
  19. 19. Mono-repo Mono-repo can grow out of control to up to hundreds of functions
  20. 20. Multi-repo More difficult to share code Complicates deployments
  21. 21. Local environment - Local testing
  22. 22. Local environment - Local testing Solution - Unit tests - PR environments for integration testing
  23. 23. Cold starts - Cold vs warm performance of functions
  24. 24. Monitoring and Logging - AWS default logging - Cloud Watch Logs - Monitoring - Limited metrics at AWS
  25. 25. Vendor Lock-In
  26. 26. Thank you!

×