AWS Lambda Room for Improvement
I can only speak from the user experience. Salesforce integrates SharesPost efficiently. How? They say, "Okay, I invented another language called Apex. Forget about anything else. This is my language." The benefit of this language is that everything is simplified. Your system is super easy to maintain. But AWS then assures you that they are flexible, that they have a collection of 10 or 20 languages, and you just choose your environment and range. That's the reason I appreciate Salesforce. They always make things easier. They have their loop reasoning because they are a different kind of company. Microsoft and AWS really get the full spec. They want to own the business. But Salesforce data wants the simplest way.
So, this is my understanding and unique experience.
I think that perhaps Lambda could explore its functionality more.View full review »
There are certain limitations to some services in Lambda which will have to be overcome over time. Primarily, I think there are two aspects of the product that are in most need of improvement.
One is, of course, the customization. The process of customizing should be simplified.
The other is specifically in the area of integration. The configuration requirements for the services which would be desirable to integrate with Lambda are not always as easy to utilize as they should be. For example, the opportunities we have to integrate solutions with the world outside of the cloud are not well supported. These integrations are supported well inside the cloud but some clients need to support solutions outside the cloud. If somebody has that need we should be able to deploy integrations with products and services outside the cloud as well.
So those are the two drawbacks and potential areas for improvement area which I would like to see corrected in AWS. Those features need to be updated because the current functionality of the product is not competitive enough today with other products in the category. I think with time they have to improve and add new features or offer other ways of integrating new services.
Senior Analyst with 11-50 employees
The kind of scenarios we can leverage in Lambda can be difficult. For example, we have a lot of their servers that provide APIs. Before, the APIs were hosted by a server. We have identified that some of them can be hosted in Lambda. That's a challenge as we're yet to think of our scenario and match our requirements in order to really leverage Lambda. That's more on us than the solution itself.
We need to better understand Lambda for different scenarios. We need some joint effort between Amazon and the users to have the users identify how they can really leverage Lambda. It's not about Lambda itself; it's about the practice, the guidance. There needs to be very good documentation. From the user perspective, what exists now is not always enough.View full review »
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.View full review »
CEO at a healthcare company with 51-200 employees
One area of improvement is to include support for more programming languages. AWS Lambda does not support a lot of programming languages. You have to write the Lambda functions in a certain programming language. We are using C++. My developer knows a couple of other languages. Python is his favorite language, but Python is not supported in AWS Lambda.View full review »
Senior Director - Technolog at a tech services company with 10,001+ employees
Lambda didn't use to support all the capabilities, if you wanted to initialize it before started serving the requests, it is not possible. In the most recent upgrades, they have added this feature. There is nothing missing. If there is something missing, AWS has other solutions that covers it. I look at Lambda as a piece of AWS, working in conjunction with other solutions.View full review »
There are several things that can be improved, including:
- It has limited access to disk space, as it does not have full access to underline VM
- Lamba functions have cold-starts that can cause some delay
- It is hard to troubleshoot and monitor Lambda functions
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.View full review »
There is room for improvement in user-friendliness. When comparing this solution to others it is not as user-friendly.View full review »
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.View full review »
Technical Architect at a tech services company with 1,001-5,000 employees
The running time of AWS Lambda runs fine. It takes around five minutes but it would be great if that time could be extended.View full review »
Sr. Technology Specialist at a computer software company with 5,001-10,000 employees
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.View full review »
IT Analyst at Tata Consultancy Services
The security needs to be improved.View full review »