AWS Serverless solution for developers
Download as PPTX, PDF1 like287 views
The document discusses AWS serverless solutions, highlighting the concept of serverless architecture and its benefits, such as lack of server management and scalability. It reviews various AWS Lambda use cases, including backend operations, DevOps tasks, and handling events, while also addressing challenges like version control and local development. Additionally, it touches on AWS services like API Gateway and X-Ray for monitoring and managing serverless applications.
AWS Serverless solution for developers
- 1. AWS SERVERLESS SOLUTION MICHAEL HABERMAN AWS CERTIFIED SOLUTION ARCHITECT FREELANCER
- 2. AGENDA • What is serverless? • Where does it help us? • What challenges it raises? • How to solve them?
- 3. CLOUD WANT TO MANAGE • Managed services • Database • Compute • Containers
- 6. WHAT IS SERVERLESS? •No access to server instance (ssh / rdp) •No instance type selection •Meet the load
- 7. GENERAL WEB ARCHITECTURE SERVERLESS
- 8. WHAT IS LAMBDA FUNCTIONS? •Code only
- 10. LAMBDA USAGES •Full backend (API) •Internal application usage (event / API based) •Devops
- 11. LAMBDA USAGES - DEVOPS •Taking an EBS snapshot •Start / stop instances (reduce cost) •Report to Slack •Change security groups •Block users (failed logins)
- 12. LAMBDA USAGES – EBS SNAPSHOT
- 14. LAMBDA USAGES - INTERNAL •S3 upload => thumbnail / watermark •Insert / pull from queue (SQS) •Respond to web hooks •Generate reports
- 15. LAMBDA USAGES – PULL FROM SQS
- 16. LAMBDA FUNCTIONS Pull from SQS
- 17. LAMBDA USAGES – FULL BACKEND •Expose API •Multiple API endpoints => multiple Lambda functions •Goes well with micro-services approach
- 18. LAMBDA USAGES – FULL BACKEND
- 19. AWS API GATEWAY •Exposes an API •Invokes a Lambda function •Other features (authentication, envs, etc…)
- 20. LAMBDA FUNCTIONS Lets create an API
- 21. AWS API GATEWAY •Who is responsible? • API gateway • API gateway proxy to lambda
- 22. QUICK REVIEW – THE GOOD •Scalable API •Monitoring •Logs •No infrastructure at all •Any trigger •Access AWS resources •DLQ •Millisecond measure •Env variable
- 23. QUICK REVIEW – THE BAD •Version control? •Developing locally? •Debug? •File system?
- 24. LAMBDA VERSION CONTROL Version #1 Version #2 Version #3 Version #4 Version #5 Alias Prod Alias QA
- 25. LAMBDA LOCAL DEVELOPMENT •Invocation •Create event payload •Using AWS resources •No official solution
- 26. LAMBDA DEBUG •No debug •Use logs
- 27. LAMBDA FILE SYSTEM •No file system access •Use S3 •AWS SDK is available by default
- 28. LAMBDA COST •Lambda • Per 100 milliseconds + memory + data transfer •API gateway • Data transfer + caching
- 29. AWS XRAY •Trace request across multiple services •Micro service oriented
- 30. QUESTIONS?
- 32. EDGE FUNCTIONS •Dynamic CDN solution