Sr Technical Specialist at a financial services firm with 10,001+ employees
Real User
Top 5
Easy to deploy and does not need an initial capital investment on servers
Pros and Cons
  • "AWS Lambda is serverless."
  • "We face some problems with the event-driven execution model."

What is our primary use case?

We have one or two use cases for real-time file processing. We use the event triggers to detect file arrival.

What is most valuable?

AWS Lambda is serverless. It is quick to deploy. The event-driven execution model has improved the project efficiency because it is quick and easy to deploy. However, it also introduced a set of new problems. It is the industry traction ever since the network went fully API.

Since the tool is serverless and it is hosted in the cloud, we do not need an initial capital investment on servers. We can pay as we use. We have integrated the product with other AWS services. We use SNS and SQL. There is an offering from AWS for integrated solutions.

What needs improvement?

We face some problems with the event-driven execution model.

What do I think about the stability of the solution?

The tool is very stable. There are certain things that we have to do to support it, but once we cross the t's and dot the i’s, it works.

Buyer's Guide
AWS Lambda
March 2024
Learn what your peers think about AWS Lambda. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.

How was the initial setup?

The initial setup seems to be very straightforward.

What other advice do I have?

I will recommend the solution to others for serverless computing needs. It’s a quick delivery. We do not have to set up servers before we start deploying. Overall, I rate the product a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Hazem Shaalan - PeerSpot reviewer
Site Engineer at Audio technology
Real User
Top 20
You can log in with the help of a post-confirmation page
Pros and Cons
  • "We are building a Twitter-like application in the boot camp. I have used Lamda for the integration of the post-confirmation page in the application. This will help you get your one-time password via mail. You can log in with the help of a post-confirmation page. We didn’t want to setup an instance specifically for confirmation. We used the Lambda function so that it goes back to sleep after pushing up."
  • "The tool changes its UI every month which is very frustrating for me. I don’t know why AWS keeps changing the UI. They can’t stick to a specific one"

What is our primary use case?

We are building a Twitter-like application in the boot camp. I have used Lamda for the integration of the post-confirmation page in the application. This will help you get your one-time password via mail. You can log in with the help of a post-confirmation page. We didn’t want to set up an instance specifically for confirmation. We used the Lambda function so that it goes back to sleep after pushing up.

What needs improvement?

The tool changes its UI every month which is very frustrating for me. I don’t know why AWS keeps changing the UI. They can’t stick to a specific one.

What do I think about the stability of the solution?

I have not faced any stability issues with the tool.

How are customer service and support?

I know that AWS has flexible support but if I encounter any problem, then I just Google it. I get a lot of support from Google, YouTube videos, and Discord channels.

How was the initial setup?

The solution’s initial setup was neither easy nor complex. I started learning about cloud services about six to seven months ago and already had a background in it. However, the implementation was not easy since a lot of errors just popped up. I had to check the CloudWatch logs and look into the bugs in the code. It wasn’t interesting. The deployment took around two hours to complete.

What other advice do I have?

I would rate the solution a ten out of ten. The solution works fine for us and we didn’t require the need to maintain it. I didn’t face any problems working with the product.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
AWS Lambda
March 2024
Learn what your peers think about AWS Lambda. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
Sai Durga - PeerSpot reviewer
Sr.Software Engineer at Xoriant
MSP
Top 5
Easy to set up with good workflows but there are issues with some integrations
Pros and Cons
  • "The initial setup is pretty easy."
  • "I have seen some drawbacks with certain integrations."

What is our primary use case?

We primarily use the solution for integration purposes. We use it very closely with Jira, for example. 

What is most valuable?

The workflow is the best thing about the product. When the integration happened and from where to where is something we can see automatically and navigate the workflow. 

From Jira to AWS Lambda, we're sending data. When we go from Jira to AWS, through webhooks, we are sending data to the Lambda function. From Lambda, they're navigating Jira. Whenever the manual rework is done, they need to perform some job bundles from the AWS to the Jira only. They can operate from Jira to AWS and AWS to Jira, which is great.

The initial setup is pretty easy. 

What needs improvement?

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. 

For how long have I used the solution?

I started using the solution six months ago. 

What do I think about the stability of the solution?

I'm not aware of any issues with stability. It's been issue-free so far. 

What do I think about the scalability of the solution?

The solution can scale. We can add more users to it. We have ten to 15 people on the product right now. They are developers. 

How are customer service and support?

I've never needed to reach out to technical support. I haven't had any issues. I can't, therefore, speak to how helpful or responsive they are. 

How was the initial setup?

We found the setup to be straightforward. It's not complicated at all. 

It took me one day to get everything up and running.

What's my experience with pricing, setup cost, and licensing?

I'm not aware of the exact pricing. I don't handle any licensing. 

Which other solutions did I evaluate?

Our company is looking into ServiceNow to see how it handles integrations. 

What other advice do I have?

We are a customer and end-user. We use the cloud for integration purposes. 

I'm not completely into AWS Lambda just yet. What I can say, integration-wise, Lambda does not require any username or password from the Jira once they start talking to each other. It's integrated very well. 

I'd recommend the solution to others. 

I'd rate the solution seven out of ten. It is a very new tool for me; I need to do some more research on it to really understand it fully.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
RANJAN KUMAR - PeerSpot reviewer
DevOps Engineer at ZoomOps Technology
Real User
Top 5Leaderboard
Enables the building of serverless applications and provides automatic scaling
Pros and Cons
  • "The most valuable features of AWS Lambda are a serverless and event-driven architecture."
  • "AWS Lambda should support additional languages."

What is our primary use case?

AWS Lambda is a serverless computing service provided by AWS. It is allowed to run the course without the provisioning or managing server and paying only for the compute time consumed during execution.

What is most valuable?

The most valuable features of AWS Lambda are a serverless and event-driven architecture. The solution provides automatic scaling and supports languages like Node.js, Python, and Java.

What needs improvement?

AWS Lambda should support additional languages.

For how long have I used the solution?

I have been using AWS Lambda for two years.

What do I think about the stability of the solution?

AWS Lambda is a stable solution.

What do I think about the scalability of the solution?

More than five people are using the solution in our organization.

How are customer service and support?

The solution’s technical support is good.

How was the initial setup?

The solution’s initial setup is easy.

What's my experience with pricing, setup cost, and licensing?

AWS Lambda is a cheap solution. The solution has a generic pricing before being triggered. After triggering, we need to pay the bill based on how much time the server runs.

What other advice do I have?

Our company decided to use AWS Lambda because it is integrated with AWS services. The solution enables the building of serverless applications and provides automatic scaling and event-driven execution. AWS Lambda can be triggered by various AWS services like AWS S3, DynamoDB, AWS API gateway, and AWS CloudWatch.

I would recommend the solution to other users. It is easy for someone to learn to use Lambda for the first time.

Overall, I rate the solution ten out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Swathi Minchala - PeerSpot reviewer
Software Engineer at Relevance Lab
Real User
Top 5
Supports multiple languages and scales automatically based on the number of incoming requests
Pros and Cons
  • "The tool scales automatically based on the number of incoming requests."
  • "The support team does not know how to implement and build the solution."

What is our primary use case?

I have to send daily reports. We have many child accounts in AWS Organizations. We need reports on the cost of the accounts. I use AWS Lambda because we have to run the code without provisioning the servers. AWS Lambda is a serverless computing service.

What is most valuable?

The tool scales automatically based on the number of incoming requests. It supports multiple languages. We can use Python, Java, and Ruby. We can use the solution to stop and start the instances.

What needs improvement?

We must at least know the basics of languages like Python or Java to implement automatic processes and daily schedules. We must learn the Lambda function and the languages to use the tool.

For how long have I used the solution?

I have been using the solution for three months.

What do I think about the stability of the solution?

I rate the tool’s stability a nine out of ten.

What do I think about the scalability of the solution?

I rate the scalability an eight out of ten. We have more than 100 users.

How are customer service and support?

The support team does not know how to implement and build the solution.

How would you rate customer service and support?

Neutral

How was the initial setup?

We must know Python or Java to implement the product. It is not easy, but it is not difficult. We need some experience.

What's my experience with pricing, setup cost, and licensing?

We only need to pay for the compute time our code consumes. The solution does not cost much.

What other advice do I have?

I will recommend the product to others. We can automate the processes and integrate the solution with other services. The product provides elasticity and automatic scaling features. Overall, I rate the product a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Ansari Rehman - PeerSpot reviewer
Cloud Data Architect (AWS-Snowflake-Teradata-Oracle) at a consultancy with 10,001+ employees
Real User
Top 5
Advantageous triggering feature but would benefit from enhanced editing functions
Pros and Cons
  • "By using Lambda, we can use Python code and the Boto3 solution."
  • "Lambda would benefit from a debugging feature as well."

What is most valuable?

I have found this solution very useful. By using Lambda, we can use Python code and the Boto3 solution. 

The triggering feature is also valuable. For example, if we are using Kafka, we need to be aware that the language comes in Kafka when we write in Python, and that we are transforming our data into the meaningful server and dumping that into the S3 bucket.

What needs improvement?

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.

For how long have I used the solution?

I have been working with AWS Lambda for one year.

What do I think about the stability of the solution?

The solution is stable. There are times when we do need to refresh when we make changes and deploy them. This seldom occurs.

What do I think about the scalability of the solution?

We have five developers using Lambda. 

How are customer service and support?

Technical support can take a long time to respond. I would rate their service a seven out of 10.

How would you rate customer service and support?

Neutral

How was the initial setup?

The initial setup of AWS Lambda is simple.

What other advice do I have?

I would rate this solution a seven out of ten overall. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
PremKashyap - PeerSpot reviewer
Solution & Integration Architect - AWS Cloud & Modernization at a tech vendor with 10,001+ employees
Real User
Top 20
Serverless compute platform used to build microservices that can be set up in multiple ways based on experience
Pros and Cons
  • "Lambda is the preferred compute option because of on-demand cost. We don't have to provision any hardware beforehand. We don't have to provision the capacity required for the services because it is serverless."
  • "The first time Lambda is started up, it takes some time to spin up an instance for serving the consumer requests. AWS has been trying to solve this in a variety of ways but have not yet managed to do so."

What is our primary use case?

We are building microservices in Lambda and exposing them via an API Gateway for the end consumer. These microservices talk to DynamoDB, or third-party APIs but can also be event-driven. These microservices carry out specific business functionalities.

We have plans to increase usage in the future. We have been modernizing our usage of SOA technology and rewriting those SOA services on the cloud using AWS Lambda. We are transitioning to a serverless environment using Lambda. 

How has it helped my organization?

Lambda is the preferred compute option because of on-demand cost. We don't have to provision any hardware beforehand. We don't have to provision the capacity required for the services because it is serverless. 

AWS takes care of things behind the scenes and we pay only for usage. We don't have to incur uptime or the upfront cost to procure a EC2 instance or create any ECS service.

What is most valuable?

You can trigger Lambda in various ways including API Gateway events or a S3 object event. You can create a file in SP and it can trigger a Lambda function. You can process the file based on the event and complete asynchronous programming. It supports both synchronous as well as asynchronous programming. It is integrated with variety of AWS services like the S3, SQS or SNS.

You can use Lambda for a variety of use cases. You just have to write a Lambda which can be in various languages including Python, Node.js or Java. There is no limit on what you can do with Lambda because it is integrated with a variety of AWS services. 

What needs improvement?

The first time Lambda is started up, it takes some time to spin up an instance for serving the consumer requests. AWS has been trying to solve this in a variety of ways but have not yet managed to do so. 

Lambda can only run for a maximum for 15 minutes. If you have a job which requires running for more than 15 minutes, you cannot use Lambda for that use case. 

For how long have I used the solution?

I have been using this solution for five years. 

What do I think about the stability of the solution?

I would rate Lambda an eight out of ten for stability. 

What do I think about the scalability of the solution?

This is a scalable solution. I would rate it an eight or nine. You can have 999 Lambda instances running at a particular second at one time. That is the default. It you need to scale above this, you can request for AWS to increase your capacity.

How are customer service and support?

I would rate the technical support an eight out of ten. We do contact the AWS support team if we are stuck or something is not working. They provide their input and we set up a call with them to explain our issues and reach a resolution.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is straightforward. They have variety of ways to set it up via the console, ETK or CFT. You can easily configure Lambda via variety of ways based on your experience. Usually, newcomers will use console which is a UI and makes your task easier. Experienced people will go with CLIs, SDPF or CFTs to create Lambda resources.

We are not just deploying Lambda. We have a variety of AWS services which we combine into one script and we do it via an AWS code pipeline.

I would rate the setup a nine out of ten.

What about the implementation team?

Deployment was done in-house by our own team. The patching of underlying hardware and other maintenance is done by AWS. 

What was our ROI?

We have experienced a ROI using this solution. I would rate it an eight out of ten. 

What's my experience with pricing, setup cost, and licensing?

Lambda is an affordable solution. They offer free requests every month and charge per the compute time. If you are working in a big organization, usually AWS offer a savings plan where you get approximately 70% discount on pricing.

If one is very affordable and ten is expensive, I would rate this solution a two out of ten. Costing is per account. Production will involve a higher cost. 

What other advice do I have?

If you are planning to implement the solution using scripting language like Node.js or Python, it's better to rather use traditional programming language like Java, or .NET, because Lambda runs faster and more efficiently. We implement it using these scripting languages as the first choice.  

It is important to understand your use case properly and if Lambda is a good fit. Solutions such as Docker, Kubernetes, OpenShift or normal EC2 instances may be a better fit for your business.

I would rate this solution a nine out of ten. It integrates well with variety of AWS services which makes the event-based programming easy. Lambda is well suited to a variety of use cases or applications.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Ashish Disawal - PeerSpot reviewer
DevOps Consultant at PraHari Tech
Consultant
Top 10
A highly scalable and cost-effective serverless computing solution, enabling seamless code execution in response to various events, with advantages including easy scalability and efficient integration
Pros and Cons
  • "The utilization of containers is particularly beneficial in overcoming the size limitations imposed on Lambda functions which not only allows us to work around these constraints but also contributes to the improvement and maintenance of our code."
  • "There's room for improvement in the testing setup."

What is our primary use case?

We use it primarily for image resizing in batch and scheduled jobs. Additionally, one of our clients relies on Lambda for running a continuously active custom API, handling their ongoing API requests.

What is most valuable?

Leveraging it to run containers directly from Amazon Elastic Container Registry has proven to be highly valuable. The utilization of containers is particularly beneficial in overcoming the size limitations imposed on Lambda functions which not only allows us to work around these constraints but also contributes to the improvement and maintenance of our code.

What needs improvement?

There's room for improvement in the testing setup. Attempting to test it through the AWS CLI also posed issues, and when trying to test the Lambda function on my local machine, I encountered difficulties in obtaining comprehensive logs or error messages to diagnose what might be going wrong.

For how long have I used the solution?

I have been working with it for one year.

What do I think about the stability of the solution?

It provides a high level of stability, and I have not encountered any issues so far. The system demonstrated stability whenever we attempted to update the function or perform any operations. Responses consistently aligned with the timeframes specified on the AWS website, remaining within the service level agreement. I would rate it nine out of ten.

What do I think about the scalability of the solution?

The scalability is notably high, I would rate it nine out of ten. Approximately sixty percent of my clients are utilizing this approach. While I serve two major organizations, the majority of my clientele consists of small and medium-sized businesses.

How are customer service and support?

The technical support from Amazon has been excellent, and I've consistently had positive experiences. During a customer migration from another cloud provider to AWS, the entire technical team provided valuable insights and enhanced the architecture. Their assistance not only improved the overall design but also ensured smooth transition and support. Even for minor issues, the response times have consistently exceeded the expectations stated on the website. For instance, if a 24-hour response time is indicated, they typically respond within twelve hours. I would rate it nine out of ten.

How would you rate customer service and support?

Positive

How was the initial setup?

I would rate the initial setup around seven out of ten. While it wasn't overly challenging, it did demand a certain level of technical proficiency. Someone without substantial technical knowledge might find it less straightforward to set up.

What about the implementation team?

In our container-based approach, we initiated by constructing containers on the local developer machine, then we pushed these containers to AWS Elastic Container Repository. Following this, we established a Lambda function that utilized the uploaded ECR image, allowing it to execute the associated container. Additionally, we incrementally built services to utilize those containers at Lambda functions. The deployment took less than three hours.

What's my experience with pricing, setup cost, and licensing?

The pricing varies based on the specific solution you're implementing, and in comparison to the value it provides, the overall cost is reasonable. When used appropriately for its intended purpose, the price is relatively low. However, if Lambda is employed outside its intended scope, the cost can escalate exponentially. I would rate it four out of ten.

What other advice do I have?

I recommend thoroughly reading the documentation to determine if it is a suitable solution for your specific use case. It's essential to understand the nuances of your use case before proceeding with the implementation. Overall, I would rate it eight out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free AWS Lambda Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2024
Product Categories
Compute Service
Buyer's Guide
Download our free AWS Lambda Report and get advice and tips from experienced pros sharing their opinions.