You probably shouldn't be using Lambda functions to serve front-end websites and assets. Use S3 and CloudFront for that. The Serverless framework has nice plugin for it. It integrates nicely into the environment as well, if you want to write an API and deploy it to Lambda functions. There are also a few plugins for warming functions you can use with the Serverless framework. Nevertheless, I'd still avoid using Lambda for database intensive APIs, while it can be incredibly useful for cronjobs, pre/postprocessing, moderate throughput APIs, and event driven computation.
Thanks for reading! I ultimately fell back on using S3 and CloudFront to paper over the latency issues with cold starts for the site--glad to hear that's what you recommend!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You probably shouldn't be using Lambda functions to serve front-end websites and assets. Use S3 and CloudFront for that. The Serverless framework has nice plugin for it. It integrates nicely into the environment as well, if you want to write an API and deploy it to Lambda functions. There are also a few plugins for warming functions you can use with the Serverless framework. Nevertheless, I'd still avoid using Lambda for database intensive APIs, while it can be incredibly useful for cronjobs, pre/postprocessing, moderate throughput APIs, and event driven computation.
Thanks for reading! I ultimately fell back on using S3 and CloudFront to paper over the latency issues with cold starts for the site--glad to hear that's what you recommend!