We have a DNS as a service and NAS as a service, which integrates, and we use Lambda functions there. We have a lot of applications that we use Lambda for.
This solution is cloud-based.
We have a DNS as a service and NAS as a service, which integrates, and we use Lambda functions there. We have a lot of applications that we use Lambda for.
This solution is cloud-based.
Some of the most valuable features are that it's easy to install and use. The performance is also good.
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.
I have been using Lambda for many years.
This solution is stable.
This solution is scalable.
I think, eventually, we will increase our usage. We need to move some of our services to Lambda.
Amazon's technical support is good.
Before implementing Lambda, we had legacy types of solutions.
The installation could be faster, but I believe it's a straightforward process. I manage a team that handles the installation, so I can't comment on the specifics of the installation process. Within the team that handles maintenance and deployment, we have two engineers.
We implemented this solution through an in-house team.
We don't need to pay for licensing to use Lambda.
I rate AWS Lambda an eight out of ten. I would recommend AWS Lambda to others. We provide a lot of services, part of which is that we write Lambda functions.
Lambda can be used for automating AWS resources.
It can also be used for automation outside of the cloud and for serverless applications. With Lambda, you can apply the code directly.
The stability of the solution is very good, as is the performance.
It's a brilliant Amazon service that provides for many use cases. It's quite flexible.
The product has been very easy to use. All you have to do is configure a Lambda function and then deploy your code directly there and then you can invoke it in different ways.
It is easy to configure.
The initial setup is very straightforward.
Technical support has been great in general.
It would be ideal if we could use the solution across different platforms.
The integration could be better.
I've been using the solution for three years at this point.
The solution is stable and the performance is great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.
We have multiple applications. Most of our applications are Lambda-based, I would say there are around a hundred at this point.
The technical support on offer is brilliant. There shouldn't be any concern with contacting them. they are helpful and responsive. We are satisfied with the level of service on offer from them.
We have found that the solution is easy to install. You just have to do it through the UI and you can easily configure it and deploy it directly.
For deployment, et cetera, we just need one cloud ops engineer per day.
I was able to handle the implementation myself. I did not need the assistance of any consultants or integrators. Individual users should be okay if they want to install it themselves.
We don't need to worry about monthly or yearly licenses.
I'd rate the solution at a nine out of ten. I've been very pleased with its capabilities in general.
I would recommend the solution to other users and companies.
The product serves as a function as a service, a serverless environment, you can say. It's a serverless environment, or, as some people call it, function as a service, FaaS.
We have been using it as a mobile backend. We have a mobile frontend, a mobile application, which uses the AWS Lambda functions running in the cloud. It serves as an API backend for a mobile application that is running in the frontend.
The solution is highly scalable.
The solution has proven itself to be stable.
The initial setup is straightforward.
We've found the cost to be very good. It would be a great option for startups due to the low pricing.
The solution is very mature.
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.
I've been using the solution for a couple of years at this point. It's been a while.
The solution is pretty mature by now. It's been there for a few years with AWS and they're continuously improving it. It's pretty mature. The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.
The solution is highly scalable and also very cost-efficient. You only pay for the time, the duration of time and that's in maybe seconds, microseconds. You pay very little until you have very large-scale users. It is ideal for startups who want to deploy applications on the cloud.
While internally only our developers really use the solution, the mobile application is used by thousands of users globally.
We do plan to increase usage and will be adding more functions to our application.
While something was used before, it likely wasn't serverless.
I'm aware that Oracle and Azure have certain options available.
The initial setup is not overly complex or difficult. It's very straightforward.
The deployment times vary. It really depends on what you need to deploy.
Our developers managed the implementation process. A consultant or outside integrator was not required. It was all handled in-house.
The solution is very cost-efficient.
We are using the latest version of the solution currently. I cannot say which version number it is. I don't know it off-hand.
I'd rate the solution at an eight out of ten. We've been pretty happy with the capabilities so far.
I would recommend the solution to other organizations. This is much better than the other serverless solutions.
AWS Lambda's most valuable feature is serverless architecture.
There are sometimes issues following an update.
I've been using AWS Lambda for about five years.
AWS Lambda is stable.
AWS Lambda is scalable.
The initial setup was straightforward and took only a few minutes.
AWS Lambda's cloud version isn't expensive, and I'd rate its pricing as five out of five.
I would rate AWS Lambda ten out of ten.
The primary use case is processing data. We use the pipeline multiple places to process the data. Whatever JSON files we get, we have to standardize, enrich, and also format to the application.
The most valuable feature is that it's serverless. Therefore, server configuration is not required, and we can run it directly anywhere. We can write Java code or Python code in that.
The initial setup is straightforward as well.
AWS Lambda is good for short-term automation processes.
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.
I've been working with AWS Lambda for six to seven months.
The initial setup of AWS Lambda is straightforward.
The cost of AWS Lambda is based on runtime.
It's a good product, and we use Lambda for short run processes, for example, processing a file from the landing zone. Suppose FTP or SFTP has put a file in one landing area, and we have to push a file to the S3 bucket. We would not need to do any writing, shell scripting, or Linux coding, etc. In general, with Lambda you can get the Python coder or Java code.
So, professionals can easily perform these tasks within a short time. This will help with agile processes and sprints. My advice is that AWS Lambda is a good service for short-term automation processes.
I would rate AWS Lambda at eight on a scale from one to ten.
Our primary use case is for our financial institutions. We use it for many customers that we work with. We develop solutions for our customers and run them on AWS. We wanted to build the solution on the public cloud and out of all the public cloud providers, AWS is the best. It has a rich set of services.
It's a serverless solution which is the best feature. It helps us because it offers free aspects. From the infrastructure perspective, it helps us manage costs. There is no overhead of estimating how much infrastructure we're going to need. We can focus on building the business functionality that we want to build.
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.
I have been using AWS for two and a half years.
We don't have any issues with stability or scalability. We have offline and online users. There are thousands of online users.
Their support is excellent. We have no complaints. It can be expensive, we bought the enterprise support. If you don't want to spend the money, you might run into issues but that isn't the case for us.
Everything was set up in the public cloud. We didn't need to set up a lot of things. We didn't have to connect a lot of connectivities to external applications. If you are setting it up on hybrid solution, there is a lot of work that needs to go in. You need to understand what your organization's security standards are, how the different teams are going to access the infrastructure, etc. For hybrid, it will take a lot of time but for only the public cloud, it is quite easy.
AWS is slightly more expensive than Azure. But from a maturity perspective, AWS is way more ahead than Azure.
I would rate it a nine out of ten. It was missing features like initialization but they are available now in the latest release.
It is good for smaller companies that don't have a lot of staff that will manage the infrastructure. It automatically scales based on the users and allocating the resources. From a cost perspective, it is quite cheap. It takes out a lot of overhead. If it's for a large company with a lot of experts, there are other good solutions.
AWS Lambda is used for the whole surface, it does the backups, and schedules, and learns some of the core functionalities but it can depend on the topic or application. The solution is used to build APIs and many other functions
AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job.
I have been using AWS Lambda for approximately six years.
AWS Lambda is stable.
AWS Lambda is in the cloud which makes it scalable.
I have worked in many companies that have used this solution and some of them had a lot of users.
The support from AWS Lambda is very good, they are responsive.
I rate AWS Lambda a nine out of ten.
My primary use case for this solution is usually for event-driven architecture. Since it's AWS, it's cloud-based.
I have found all of the features valuable. It's an easy and cheap solution.
AWS Lambda could be improved by increasing the size of the payload. Also, sometimes Lambda doesn't implement well for bigger solutions.
I have been using this solution for three years.
This solution is stable.
I would rate customer support a nine out of ten. I have made three or four service requests and those were all resolved within 24 hours.
I didn't use a different solution before implementing Lambda.
The installation is straightforward. There isn't really anything you need to do. If you know exactly what you want, it can be done in five minutes.
I implemented this solution myself.
I pay for a monthly license. The licensing options will depend on the users. There's a monthly option and a yearly option.
Lambda is a good and cheap solution and I would recommend it to those without a huge payload. There are around twenty or thirty people using Lambda in my organization.
I would rate this solution an eight out of ten.