3 ms·

- Monitoring & debugging is little hard - CPU power also scales with Memory, you might need to increase it to get better responses - Ability to attach many st

by CSDude 9y ago

- Monitoring & debugging is little hard - CPU power also scales with Memory, you might need to increase it to get better responses - Ability to attach many streams (Kinesis, Dynamo) is very helpful, and it scales easily without explicitly managing servers - There can be a overhead, your function gets paused (if no data incoming) or can be killed undeterministically (even if it works all the time or per hour) and causes cold start, and cold start is very bad for Java - You need to make your JARs smaller (50MB), you cannot just embed anything you like without careful consideration

deleted 9y ago
[deleted]
AlexanderC89 9y ago
@CSDude you can check out this small tool i've written for debugging Lambda and API Gateway integration. https://github.com/AlexanderC/lambdon https://github.com/AlexanderC/lambdon (i know the name sucks) Also @chetanmelkani as a hint: if you are using NodeJS runtime most optimal from the execution time and cost efficiency perspective is setting up 512mb of memory ;) it's about getting x2 performance boost over the 128mb configuration.