What do you like best?
1. Running my code in a container at a faster pace.
2. I don't need to worry about the infrastructure
3. Hassle free scaling based on business requirements and traffic
4. Consistency in performance while scaling containers
5. Most important- billing is optimised with millisecond usage Review collected by and hosted on G2.com.
What do you dislike?
1. Not suitable for high memory consumptive apps as it has large memory footprint is up to ~3000Mb
2. The maximum payload supplied to a function is up to ~6Mb only (request/response) for synchronous calls and 128Kb for asynchronous calls
3. Any deployment package larger than 50Mb is not allowed directly rather need to upload the same to s3 bucket. Review collected by and hosted on G2.com.
AWS Lambda Reviews
What do you like best?
Very simple & easy to use in order to deploy a little piece of code.
Lot of runtime are available :
- Python (2.7... 3.8)
- Node.js (10, 12)
- Java (8, 11)
- Golang (1.x)
- Ruby (2.5, 2.7)
More over, you don't pay when there is no activity. Review collected by and hosted on G2.com.
What do you dislike?
When deploying a lambda, you have to know what a VPC is. It's a pity to care about network.
More over, you have to take care about cold start : when using heavy runtime, the first request may be long to start. Review collected by and hosted on G2.com.
What do you like best?
There are a lot of things best about AWS Lambda. AWS Lambda is a serverless service which means we don't have to worry about server management. Just upload the code and run it. You only pay for what you have executed. The price of the AWS Lambda service is too less. It can be integrated with many other AWS services making it useful for developing micro-services, cron-based or event-based services, REST APIs, etc. We don't have to worry about its high availability or auto scaling as it is a fully managed serverless AWS service. Review collected by and hosted on G2.com.
What do you dislike?
The execution time should be increased as 15 minutes of execution time is sometimes where less. Also, we should get an option to modify the processing power (CPU) separately and not by the memory (RAM). Also, we should get the capability to run as many Lambdas as possible in parallel at a time by making this option selectable at the time of creating the AWS Lambda function so that we don't have to worry about requesting the increase in this soft limit as well as let us know the maximum hard limit for this configuration beforehand. Review collected by and hosted on G2.com.
What do you like best?
The best thing about it is simple, just charge as to what you're using and it's open source! Without the need to control the operational service pile, focus purely on the script you have to do. I including how to create code by using the Web or mobile app. It is also always updated to make use of the latest features. Review collected by and hosted on G2.com.
What do you dislike?
We create less scripting servers that are used to automate our infrastructure. This enables data to be easily parsed and business logic performed and transmitted to the next necessary service Review collected by and hosted on G2.com.
What do you like best?
For me Amazon Lambda is excellent, with easy code to test, very easy to configure, which gives me the opportunity to write codes in several languages, very simple to learn and you only pay for the time that is consumed since there is no charge while code is not running Review collected by and hosted on G2.com.
What do you dislike?
I found testing somewhat difficult at first. Review collected by and hosted on G2.com.
What do you like best?
I can divide the backend request into processes with AWS Lambda, which could be installed and housed as individual divisions of their own scale. Maintenance is much easier because the use of a lambda architecture is easy to insulate and fix without influencing both other items. Review collected by and hosted on G2.com.
What do you dislike?
Interconnection and connectivity between various Lambda functions and some other services can become much more intertwined with the growth of the system. Review collected by and hosted on G2.com.
What do you like best?
Do not lie, and use AWS lambda of how you use. This helps you to pay for just computing time and instantly executes the code from the smartphone or web program. AWS Lambder wants to take care with all you need to execute the machine and scale up your application with data access, which helps developers to easily scale up to users' experience, rather than tuning and reformatting systems It is more sensitive to device changes that notify data shift. Review collected by and hosted on G2.com.
What do you dislike?
The language functionality of AWS Lambda is very small. The method of repairing is really complex. With the progress of the scale, this service becomes very expensive. Awareness of the user interface of AWS Lambda will help to restore it. It is just not impractical, and that does not give a dignified image of the value of the service performance. That is a confounding method and misuse is very simple. Review collected by and hosted on G2.com.
What do you like best?
Accurate schedule execution without fail a single time.
Different types of schedule expression that help us to execute exact time, that may be every year, month, day, hour, minutes, second.
rate and cron two types of functions that help us as per our requirements.
Server less architecture. Review collected by and hosted on G2.com.
What do you dislike?
Once we create lambda function in AWS service, we can not change name of that function.
So we have to delete it and re-create it. Review collected by and hosted on G2.com.
What do you like best?
Because Lambda is serverless technology, it allows you to focus on the code and logic of your application, without having to worry about maintaining a server. It is remarkably affordable, with the first million monthly invocations free. Review collected by and hosted on G2.com.
What do you dislike?
The biggest downside of Lambda is the cold start time. Your code runs in a container and has to be loaded onto a server before it can run. This can take several hundred milliseconds and impacts performance for the calls that suffer from needing to load the code. Review collected by and hosted on G2.com.
What do you like best?
What I like the best is that, instead of maintaining a server for all our backend needs & features, we can deploy our backend API's as a microservice, & can manage them from the AWS Dashboard, without any hassle, & along with all this, solves the problem of server maintainence.
Also, we don't have to manage a server on our own, & even have our own server for it, AWS solves that problem for us, by creating a MicroService of an API for us. Review collected by and hosted on G2.com.
What do you dislike?
What I dislike is the Lambda Obstacles, as when we sometimes try to deploy or act upon the Lambda API's from other sources or other origins, we are unable to do that.
Also, we are unable to Deploy the API's anywhere, other than our S3 Bucket Deploy, & so, even while we would like to stop using S3 Services, & move with our own Service, we would have to create the APi's from scratch itself, making it a huge problem & a task to be handled. Review collected by and hosted on G2.com.
What do you like best?
AWS Lambda is great for running code snippets in background which will automatically scale your code, you don't need to manage servers. we used it to triggers code in backgrounds like sending emails to groups, running scheduled task to generate reports and files.
If you have data to process in background or event real time without considering processing power or servers, this is best suited environment. Review collected by and hosted on G2.com.
What do you dislike?
Sometimes it gets complex when you have multiple lambda services running and trying to process same data, you need robust architecture of application to manage this.
You don't have a control over resources you are using for lambda. you cant install packages on servers which you need to process data. Review collected by and hosted on G2.com.
What do you like best?
I enjoy most about Lambda that is the dominant serverless option, meaning that it has excellent backing and support from AWS as well as the community Review collected by and hosted on G2.com.
What do you dislike?
I dislike that it is complicated to get started coming from a more traditional runtime mindset Review collected by and hosted on G2.com.
What do you like best?
The best part of this is it's simple, you only have to pay for what you use and it's serverless! No need to manage the entire server stack, just focus on the code that's important to what you need to accomplish. I like how you can use the web or mobile application to create the code. Also it's always updated so you can leverage the latest functionality. Review collected by and hosted on G2.com.
What do you dislike?
The dashboard / interface is a bit difficult to write code in, there is a limit to how much code can be used in the online editor, and I've noticed some delays in code performance with certain functions. Review collected by and hosted on G2.com.
What do you like best?
The best feature is how easy it is to integrate with the rest of AWS Services, it helps in executing code or event triggered from other services of AWS. Review collected by and hosted on G2.com.
What do you dislike?
Initial learning curve is steep and the User Interface could be made simpler. Review collected by and hosted on G2.com.
What do you like best?
Lambda is easy to use and understand. You can integrate it into many other architectures and services easily. Review collected by and hosted on G2.com.
What do you dislike?
Lambda’s GUI can be slightly laggy at times and the error output doesn’t always print all the logs. Luckily you can go to cloud watch to view all these logs however it can be a pain to switch service to service Review collected by and hosted on G2.com.
What do you like best?
* AWS Lambda is very easy to setup & deploy serverless computing platform.
* AWS Lambda supports large variety of language including Node.js, Java, C#, etc.
* After deploying application to Lambda, developer does not need to worry about scaling &
concurrency.
* Cost can be reduced drastically as we do not need to keep server up & running 24x7.
* It is pay per use model, which is great.
* Can be best used for Microservice deployment. Review collected by and hosted on G2.com.
What do you dislike?
* There may be something people don't like about Aws lambda like the memory range is limited. But
there is a lot you can do with such range.
* Also for some people code, deployment packages may be a reason for concern due to its limited size
to 50mb only.
* There may be a solution to this limitation soon Review collected by and hosted on G2.com.
What do you like best?
Pay for what you use, don't be cheated , just use AWS lambda. this allows you to only pay for compute time and automates code runs from mobile or web application. it is very responsive to system changes which can be inform of data change, AWS Lambder takes care of everything required to run and scale your code with high availability which makes scaling seamless to developers allowing us to concentrate on user experience than spending time tweaking and configuring systems Review collected by and hosted on G2.com.
What do you dislike?
It has a steep learning curve and configuring it to a functional state takes a little bit of time in the beginning. Review collected by and hosted on G2.com.
What do you like best?
AWS Lambda may run on different languages as part of serverless service. You may run in manually for test or as part of API Gateway or many other AWS services.
You may share AWS Lambda code with other teams. Review collected by and hosted on G2.com.
What do you dislike?
Cold start. After 15-30 without activity, the first request will take about 15 seconds due to cold start Review collected by and hosted on G2.com.
What do you like best?
With AWS Lambda I can break down a backend application into functions that can be deployed and hosted as separate units that scale on their own. Maintenance is easier because it is easy to insolate failing using in a lambda architecture and fix it without affecting the other units. Review collected by and hosted on G2.com.
What do you dislike?
The interconnection and communications between different Lambda functions between themselves and other aws services can get very entangled as the application grows. Review collected by and hosted on G2.com.
What do you like best?
being able to run code as a service, we are using Lambda to run some code to back up some other Amazon services using this feature, this is run completely serverless and we aren't paying for any EC2 costs! Review collected by and hosted on G2.com.
What do you dislike?
it takes a while to get your head around the lambda feature and all the different adds on you can use, it's a lot for someone who is getting started with lambda to get their head around. Review collected by and hosted on G2.com.
What do you like best?
Lambda was very simple to set up. It is literally simple to set up in tandem with AWS API Connector and RDS infrastructure, and leaves limitless potential. Lambda links directly to the Gateway providing fast communication between the two systems and from there Lambda manages the rest. Review collected by and hosted on G2.com.
What do you dislike?
In. Net, the device destroys as the period goes by without having any order, which requires just few seconds to continue. This will become probably time for other users because there are multiple connections between various systems making calls to one another. Alexa's self-hosted abilities use lambda functions internally so you can't see that in any AWS account once you build one. It will be good to see some more thorough errors to handle and catch. Review collected by and hosted on G2.com.
What do you like best?
No headache of managing servers and concentrate only on building code or logic
It is better developer workflowsith git and command line deploys vs uploading zips to lambda Review collected by and hosted on G2.com.
What do you dislike?
When several lambda run in the same region the performance goes down drastically. Review collected by and hosted on G2.com.