Deploying serverless apps in AWS Presenter: Thanh Nguyen

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

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

Lambda function on AWS

Lambda execution model

Anatomy of lambda function

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)

How serverless starting

3-tier architecture VS serverless architecture

Principles of serverless architecture - Write single-purpose stateless functions (single responsibility principle) - Create thicker, more powerful front-ends - Embrace third-party services

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

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

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

Compute as backend

Compute as glue (pipeline)

Demo