Download to read offline
Uploaded byDiego Pacheco
Serverless
This document discusses serverless computing. It notes that serverless computing abstracts away servers by treating code execution as a service, which can reduce infrastructure costs. It also lists some benefits of serverless computing like reduced provisioning and automation costs. It provides examples of serverless platforms from AWS, GCP and Azure and potential use cases. It also outlines some limitations and challenges of serverless computing.
More Related Content
Serverless
- 1.
- 2. @diego_pacheco ❏ Cat's Father ❏Principal Software Architect ❏ Agile Coach ❏ SOA/Microservices Expert ❏ DevOps Practitioner ❏ Speaker ❏ Author diegopacheco http://diego-pacheco.blogspot.com.br/ https://goo.gl/eEqvzl About me...
- 3. Serverless: IT Artof Bad Manning Continues... “Services not Servers”
- 4. Functions as FirstClass Citizen: More Abstractions! “Architecture and Operations Simplification...”
- 5.
- 7.
- 8.
- 9. Reduce Infrastructure COST ❏Such as: ❏ Provisioning ❏ Telemetry ❏ Observability ❏ Automation ^
- 10. Where the Moneygoes? (Engineering/People x Vendors)
- 11. Big Vendors AWS LambdaGCP Cloud Functions Azure Functions
- 12.
- 13.
- 14.
- 15. AWS Lambda: Anotherway to CONSUME Cloud Services!
- 16. AWS Lambda StepFunctions
- 18.
- 19.
- 20.
- 21.
- 22. There Are limitations ❏Other Limits: ❏ 5mim max time to run lambda ❏ Total number of lambdas ❏ No Debugging
- 23. Other issues andchallenges... ❏ Lambda VPC X EC2 VPC ❏ Versioning ❏ No Debugging ❏ API Breaks ❏ Long Running Jobs ❏ WarmUp x Hidden Cache
- 24.
- 25.
- 26.
- 27. Cloud Native ❏ Containers:Isolation and Portability ❏ Dynamic Orchestrated (resources optimization) ❏ OSS First ❏ Microservices Oriented ❏ Microservices requires some other concerns like: ❏ Automation ❏ Registry/Discovery ❏ Distributed Tracking / Observability ❏ Anti-Fragility / Chaos Engineering ❏ Cloud Gives you: ❏ Elasticity(Auto-Scaling) ❏ On-Demand model https://www.cncf.io/
- 28.
- 29.
- 30.