AWS

In one of my recent project I got an opportunity to work on a Java based Lambda function. Here I am sharing few tips to reduce the cost and solution to the common AWS Lambda problems like Cold start. Keep them warm! Use provisioned concurrency – AWS feature. Use Periodic ping e.g., health checks! Load as much as you can/need during runtime bootstrap since you get boosted CPU access during that time but mind the 10 second limit Keep JAR size as small as possible, avoid including unnecessary jars and classes....

You can invoke your Lambda function locally by using the sam local invoke command and providing its function logical ID and an event file. We have built a framework using AWS SAM SDK and Pytest to test our Lambda functions before every production deployment. The tests are run inside the Jenkins server itself. No dependency on real AWS account. Read more here: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html I’ll update the post with more information very soon....

Cold Start AWS Lambda: Burst Limitations – concurrency. Time, Memory and CPU limitations Only time and memory is configurable. AWS Allocates other resources like CPU, networking throughput based on selected memory configuration. Temp storage limitations – 512 MB (If need be, we can mount AWS Elastic File System) Not recommended to use libraries like Spring, Hibernate, etc. No APIs for IoC, Localization, interaction with shared services, and so on....