Upgrade to Pro — share decks privately, control downloads, hide ads and more …

AWS Lambda function

AWS Lambda function

- Introducing serverless
- Lambda best practices
- Principles of serverless architecture
- Serverless pros and cons
- Common serverless architecture
- Demo

thanhgit

May 04, 2022
Tweet

More Decks by thanhgit

Other Decks in Technology

Transcript

  1. Deploying serverless apps in AWS Presenter: Thanh Nguyen

  2. Content - Introducing serverless - Lambda best practices - Principles

    of serverless architecture - Serverless pros and cons - Common serverless architecture - Demo
  3. Marketing buzzword: Serverless ? - Serverless is a method of

    deploying and running applications on cloud infrastructure. Serverless platform provider is responsible for capacity, scaling, balancing and monitoring - Characteristics of Lambda function: - Go to market - Low cost, adapt at scale - Build better applications, easier
  4. Lambda function on AWS

  5. Lambda execution model

  6. Anatomy of lambda function

  7. Lambda best practices - Minimize dependencies - Leverage “Max memory

    used” to right-size your functions to optimize cost - Delete large unused functions (75GB limit per region)
  8. How serverless starting

  9. 3-tier architecture VS serverless architecture

  10. Principles of serverless architecture - Write single-purpose stateless functions (single

    responsibility principle) - Create thicker, more powerful front-ends - Embrace third-party services
  11. Serverless pros and cons - Serverless is not a silver

    bullet in all circumstances. But serverless architecture are the latest advance for developers and organizations to think about, study and adopt
  12. Serverless cons - Not good for latency-sensitive apps - Lambda

    runs in the public cloud, so mission-critical apps shouldn’t be based on it - Increase complexity when moving from a monolithic approach to a more serverless approach
  13. Serverless pros - Serverless architecture allow developers focus on software

    design, code rather than infrastructure - Low cost, less code, scalable and flexible is good fit for startups that want to innovate and move quickly - For example: - Netflix use lambda to automate validate for backup completions - ConnectWise use lambda to process logs such as: extract, transform, load jobs, real-time file processing
  14. Compute as backend

  15. Compute as glue (pipeline)

  16. Demo