AWS Kinesis with Lambdas: Lessons Learned

Re:AWS Kinesis with Lambdas: Lessons Learned by dbllxr on Friday July 13, 2018 @03:08PM (#17525783)

> For us, increasing the memory for a Lambda from 128 megabytes to 2.5 gigabytes gave us a huge boost.

> The number of Lambda invocations shot up almost 40x.

One thing I've learned from talking to AWS support is that increasing memory also gets you more vCPUs per container.

-----

Serverless is great in scaling and handling bursts, but you may find it VERY difficult in terms of testing and debugging.

A while back I started using an open source tool called localstack[1] to mirror some AWS services locally. Despite some small discrepancies in certain APIs (which are totally expected), it's made testing a lot easier for me. Something worth looking into if testing serverless code is causing you headaches.

[1]https://github.com/localstack/localstack

[ Parent | on HN ]

Re:AWS Kinesis with Lambdas: Lessons Learned by nikhilkuria on Monday July 16, 2018 @02:17AM (#17539153)

Thanks! For testing on our local machines, we use SAM Local, https://aws.amazon.com/blogs/aws/new-aws-sam-local-beta-buil... . This has very similar capabilities as local stack. Still, there is always a delay from a service being released by AWS to it being available on tools like Serverless or AWS local.

[ Parent | on HN ]