What do you like best?
There are a million amazing things to speak when it comes to amazon lambda. To begin with, imagine you have some code, maybe multiple API calls, or the chatbot needs to redirect the NLP data to Alexa, but you do not know all the configurations that need to be done, with deployment as well as connections configuration. And here comes lambda, a code that can manage multiple tasks for you. For example, you have your participant's data in the S3 bucket. Now, as soon as the participant submit'ss his file(let us say a sketch) into this folder, a trigger calls your lambda function. Here, the hero enters and save the day by doing whatever is necessary. If you want, your lambda function can point to an AWS SNS service that tells the user in an email that his entry has been successfully submitted. And with that too, it can perform some simple tasks like uploading the data to the judges folders, or complex tasks like performing an image analysis, and finding the desired result on the basis of ML decided. You can configure and limit it to the users who can access it, how much memory it can take, and what triggers are connected to and from it. It is amazing awesome , the only thing you need to be careful with is the Access key and token secret.
What do you dislike?
The first and foremost thing that I did not like is the documentation that AWS had done for the eclipse plugins, hence same goes for lambda as well. I had a hard time trying to figure out ways to do things in lambda all by myself or Stackoverflow. Along with that, the UI for lambda is good, but not suggestive and has no intellisense kind of technology supporting it. It would have been amazing if, as soon as I upload my code, amazon lambda would automatically do the predicted configuration based on my code, like finding and setting up the handler method, etc.
Recommendations to others considering the product:
If you plan to use lambda, probably you should look for some tutorial, or wander in stackoverflow, the documentation can only guide you to installing the aws-sdk. Then, you're all on your own.
What problems are you solving with the product? What benefits have you realized?
Using AWS lambda, we are loading implementing the below mentioned scenario in agile:
There exists and API that loads data into the back-end, i.e. weblogic coherence from a csv file. So, as soon as a file enters the S3 bucket's desired folder, the lambda function is triggered. This function invokes the API with the file url as a parameter, but before that. All validation and data-analysis have been performed by the lambda function on the data in the file so that the API gets neat data to process and input into the cache/database.