Build a 100% Serverless Website with AWS in 7 Easy Steps

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by scarface74 on Thursday October 25, 2018 @03:00PM (#18303580)

On top of everything you said, if you put your database inside your VPC, your lambda function has to create a network interface inside the subnet. That increases the cold start time.

DynamoDB is a much better solution for serverless since it just uses a REST interface.

I’m a big fan of lambda but not for user facing API end points. It works well for eventually consistent event processing.

Setting up a Load Balancer and an Autoscaling group is not rocket science. Neither is automated patch management.

[ Parent | on HN ]

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by benfrancis111 on Thursday October 25, 2018 @03:37PM (#18303899)

Aws serverless Aurora... API interface, fully mysql / postgres compatible, cheap to run - billed on a cpu minutes used basis, massively scalable, auto backup and its much faster than typical dedicated server setups. Amazon's best performing aws product ever they were saying.

[ Parent | on HN ]

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by scarface74 on Thursday October 25, 2018 @04:43PM (#18304415)

Aurora is not the issue. The issue is a lack of connection pooling and the creation and destruction of ENIs when using Lambda with anything inside of a VPC.

If you want to do anything with user facing APIs, suck it up and spend $10 a month for two or three micro Linux instances set up in an autoscaling group behind a load balancer.

Elastic Beanstalk makes it dead simple.

[ Parent | on HN ]