| It's not just lockin. It's troubleshooting Lambda. Here's a couple of questions and answers we've recently delved into: - How do I avoid a cold start? (Fake calls into the system to the point where AWS has to start more instances of your application) - Why is my cold start time different between development to production? (Production is in a VPC, which has greater instance spin up times) - Why has Lambda stopped executing on my Kinesis stream? (Oops, AWS' bad) - How can we get more parallel Lambda processing on a Kinesis stream? (Clone the stream and attach to the cloned stream) - What can I do to reduce the cold start costs for Java? (Specify your objects as static, since those are evaluated at JVM startup, which AWS doesn't charge you for) - How do I do Infrastructure as code? (CloudFormation; expect an average of 4 CF objects per function. SAM makes the CF more user friendly, but it's harder to debug and encourages the creation of extra infrastructure) - How do I increase the bandwidth allocated to my Lambda? (Increase the memory allocation) |
Well Java was the first mistake if you want a reasonable startup....