My engineers work with it on a daily basis. I just don't have enough depth of knowledge about what kinds of edge cases they may have tried and found lacking. There may be some issues with some language support at one point or another because we couldn't get the underlying libraries in there. A lot of what we do is either in JavaScript, Python, or some of the non-compiled languages. I'm not sure if we've ever tried building a C# solution, for instance, in Lambda or a Java solution in Lambda. It doesn't mean those aren't its capabilities. I would rather refer to my engineers for where the boundaries are.

What could be improved in AWS Lambda is a tricky question because I base the area for improvement on a specific matrix, for example, latency, so I'm still determining if I can be the judge on that. However, room for improvement could be when you're using AWS Lambda as a backend, it can be challenging to use it for monitoring. Monitoring is critical in development, and I don't have much expertise in the area, but you can use other services such as Xray. I found that monitoring on AWS Lambda is a challenge. The tool needs better monitoring.

Another area for improvement in AWS Lambda is the cold start, where it takes some time to invoke a function the first time, but after that, invoking it becomes swift. Still, there's room for improvement in that AWS Lambda process.

In the next release of AWS Lambda, I'd like AWS to improve monitoring so that I can monitor codes better.

The user-friendliness of the solution could be improved. If it was easy to run with the same function in other platforms, other environments, that would make it more portable. That would be really good. User-friendliness and portability will be the two factors that need the most improvement.

The startup time sometimes needs to be faster, so that is one area of improvement. The startup time of each function can be slow. When it works the first time, it takes a little bit of time, so there's a minor delay. That could be improved.

The support of additional languages would improve the solution.

There's room for improvement in the solution's warm start, which refers to the minimum time it takes to start up a Lambda function if you haven't been running it. 

The solution should continue to streamline integrations with AWS services. 

At one point, there was an issue receiving support for a new version. Support was behind by two versions and this presented challenges, but they caught up over time. 

I can't recall any features that might be lacking. For us, it works quite well, however, it depends on what a company needs.

We'd love to see more integration potential in the future.

From a very high-level perspective, it is a good solution, however, there are certain limitations. This becomes challenging for us. Specifically, a limitation is Lambda cannot continuously execute for more than 15 minutes. That could be one limitation. On an implementation level, there are certain limitations that I know about yet would not be the best person to explain as I am not technical.

The timeout for execution can be increased so that if we have a lengthy process, it will not fail before their timeouts. We've had to revamp the way that it works due to that 15-minute timeout limitation.

The execution time could be better. One of the major limitations is the time period because it doesn't give you more than seven minutes. So, before thinking about Lambda, you should think through your use case and ensure it's a good fit. Otherwise, you can use batch, step functions, or other methods. 

Reports and the monitoring board could also be improved in terms of alerts. The threshold alerts are there but can be improved. It takes some time to get used to these methods and get the hang of them. 

The product could make the process of integration easier. 

The could be more integration testing. The internal is great with Lambda, however, I have to make sure I have done my tests on a related machine before deploying.

I don't have much experience after six months. I can't speak to the pros and cons. 

I have seen some drawbacks with certain integrations. 

The 60 seconds limitation with the consumption of the service is really restrictive for a service and the solution can be improved by eliminating that.

AWS Lambda's cold start needs to be improved. It has to warm up first, and so, the response time is slower.

Another challenge I've noticed is that there is a limit to the environment variables such as the 4 KB limit. Although, the advice is to use parameters or other things to store the details when the limit has exceeded the data, this adds additional intensity to the application. If the size limits for environment variables can be revealed, it would be helpful. Even if we have to pay for it, at least we would know that we are not dealing with latency. So, I would like to see the size of the environment variables increased.

It would be ideal if we could use the solution across different platforms.

The integration could be better.

It can be a bit difficult to switch between accounts when creating services for customers. 

There is room for improvement in user-friendliness. When comparing this solution to others it is not as user-friendly.

If you want to run processing data, which takes less than 15 minutes, then you can use Lambda. However, if it is a specific ETL process or a long-term one, then AWS Lambda is not a good option.

The longer Lambda runs, the higher is the cost incurred because the cost is based on runtime.

At times, it hard to know when Lambda should be used and when it should not. So in the future, if there are serverless extensions, it would be fine.

AWS Lambda can improve its file system-based sharing capabilities and restrictions.

Lambda could be improved in the sense that some of the things done with Lambda function take some time. So the performance could be better and faster. 

We don't have the inbuilt modules in AWS Lambda. If more modules were built into or integrated with AWS Lambda, that would help developers to code.

AWS Lambda could be improved with better stability. 

AWS Lambda could be improved by increasing the size of the payload. Also, sometimes Lambda doesn't implement well for bigger solutions. 

I would like to see a find and replace function as part of Lambda's future releases. Currently, if we want to replace a code, we copy the code into Notepad, then find and replace it, and then copy that to Lambda. This would improve the editing function of the product.

Lambda would benefit from a debugging feature as well. For example, if you want to debug code running in Python and deployed in Lambda, it would be beneficial to have a debugging feature.

The deployment process is a bit complex, so it could be simplified to make it easier for beginners to deploy. 

Lambda's dashboard could be more user-friendly and customizable. I want the dashboard to have more information to quickly identify what functions and events are running. Also, we want to be able to add more trigger points, push notifications, and events. For example, we have a shopping website, so we want to create some events to trigger batch notifications like SMS.

Its price should be improved. Its pricing is on the higher side. 

I am not sure if it currently supports the Go language. If it doesn't support the Go language, they can introduce it.

I wish to see better execution time in the next release. 

I would like to see more integration with other platforms.

Its performance can be improved. There should also be more dynamic security permissions.

AWS Lambda could improve by having no-code or low-code options because currently, you need to be able to write code well to use it.

The automation with other Amazon products could be better. 

AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job.

I believe Lambda security needs to be improved.  

The overall performance of this solution could be improved. We would also like to have better integration with other AWS features. 

The metrics and reporting for this solution could be improved. 

AWS Lambda's GUI could be improved with a twist or tweak in its look and feel to make it more impressive.

There are sometimes issues following an update.