4 ms·
Connecting them traditonally to a Postgres database doesn't work well. The response to scaling issues is to either increase the number of connections to a stupi
by kennydude 7y ago
Connecting them traditonally to a Postgres database doesn't work well. The response to scaling issues is to either increase the number of connections to a stupid level, or just spend more money on a database (more than it would cost for traditional servers on AWS).
Personally, I would hold off converting everything to Lambda and once everything is on AWS, identify things which can run properly in Lambda and spin them off. Your time is probably more worth it using traditional servers than figuring out each little caveat with Lambda (and every other AWS service you'll need to integrate with. It's painful if you miss one little detail...).
- soates 7y agoThanks for you input :)
- anthony_barker 7y agoHere was their response. I understand they are improving things? - Ensure your lambda is in the same vpc. Configure the security groups correctly. Things to keep in mind - Lambda in a VPC has longer cold start as it needs to setup the relevant network interfaces - Lambda won't have internet access, you will need a NAT gateway/instance if you need internet within the lambda.
- kennydude 7y agoIt was the Postgres server running out of available connections because Lambda doesn't let you kill them when the Lambdas are kept warm. No idea if it's improved, I left the company they were doing that with. I much prefer owning your own infrastructure where possible.
- anthony_barker 7y agoThis announcement not sure it will make things better https://aws.amazon.com/blogs/compute/announcing-improved-vpc-networking-for-aws-lambda-functions/ https://aws.amazon.com/blogs/compute/announcing-improved-vpc...