Java, including SpringBoot, performs very well, but has a slow start. If you're doing ETL/data processing then you don't really care about the slow start (versus serving real time requests to end users). You will need to use larger RAM/CPU but it works fine. Quarkus, Micronaut, and Spring via Graal are all good options as well. More on reddit.com

I have created a state machine and some java lambda functions. But the code editor does not support java. Upload from option is available here with 2 different formats: ... What kind of file do we need to upload over here? Can anyone show me some sample files? Is there any pom file we need to upload for the working of state function? ... docs.aws... More on stackoverflow.com

We decided to go against it. As frameworks go it is quite heavy and with lambdas you don't need to be concerned so much with routing and servers. Lambdas are best kept small, almost at the function level. I have seen them best work with much smaller dependency injections like guice or dagger to help maintain a good structure and avoid anti patterns along side a build tool like maven. Hope this helps More on reddit.com

Keep it simple and you will be good. We follow the following for all our lambdas: Use plain SQL query instead of jpa don't use Spring Boot or any other framework if your use case is simple you don't need dependency injection for simple use case that involves couple of classes. Just create static objects and pass them around. Create objects ( eg objectMapper, AWS clients) only once use RDS proxy instead of creating DB connection directly use SnapStart use shadow jar use minimal dependencies.. exclude unnecessary transitive dependencies if you do http calls to other services make sure they are performant. If possible use async calls, parallelize calls if possible use lightweight objects, don't use xml, Json libraries if you can(most of the time simple String append is faster) run the lambda locally and profile it etc More on reddit.com