AWS Lambda

Pros

It has the best serverless solution we can use many languages and its integration with other AWS Services is also a great point towards this product through which we can easily connect all other services.

Cons

It has the Limit for the cache folder which is a limitation. Time Limit on execution is one more limitation

Pros

We have been moving from tradicional EC2 servers into Lambda Serverless. They are soooo inexpensive, we payed hundreds and even thousands of dollars in tradicional servers, and with the same functionality in lambdas we pay $100 or $200 with more than 10,000 users. Also they are very easy to scale up for many users

Cons

It is a little difficult to understand the new serverless paradigm, but once you learn to design it, it is easy. In someways is difficult to maintain, because you end up with a lot of Lambdas

Pros

That I really don't have to buy a server for a small websites

Cons

Even for a small change/integration, I have to use there other services which charge little money

Pros

-Works every time without any issues
-Easy code deployment with Python
-Scales very effectively
-Very cost-effective for testing POCs
-Medium cost for production-level workloads
-The architecture videos are great and the tutorials are good
-Great integration with Step Functions

Cons

-Costs can get out of control if things start to fail and retry policies are repeat
- Cost estimate is difficult while starting to write the code in Lambda vs servers

Pros

It allows the development of very heterogeneous applications thanks to its strong flexibility. Another strong point is the price which is calculated only for the CPU time that is used.

Cons

It is so flexible, but just as difficult to debug if something is working correctly and you cannot establish a base cost given its way of calculating costs.

Pros

AWS Lambda is a platform where you can implement REST services, Data Processing and many other things easily. What I love the most is the integration with 'Serverless' platform which support managing lambda service implementation, debugging, deployment & monitoring quite easily.

Cons

So far I haven't come across anything that made me concern about working with AWS Lambda.

Pros

One of the best thing about AWS Lambda is it support multiple triggers from queue in real time like HTTP request. It provides easy and scalable solution.

Cons

The feature which can be improve or add in AWS lambda is it takes too much time consumption for creating the container and which should be reduce.

Pros

Used AWS Lambda for couple of years. It really helped us to automate AWS cloud services. Most importantly it improves over support, customer service and monitoring. For hosting micro services it is very cost effective.

Cons

Poor design can sometimes leads to problem when call other services from AWS Lambda, some wait time is also observed.

Pros

By using AWS Lambda we make the use of all resources that we are using, that means they are very cost effective. We only pay for the service we use and they are very cheap compared to other compute services like AWS EC2.

Cons

Sometimes it's difficult to create the Lambda function with the new AWS services and we are lacking with the expertise.

Pros

AWS Lambda is very flexible, comprehensive and AWS's team tend to be aligned and in sync with ecosystem language support such as Node.js versions and in-specific Node's Long Term Support. Lambda has been one of the most successful product stories for serverless at AWS and for a long-time now and it shows in the performance and connectivity options you get to integrate Lambdas into the rest of the AWS services like API Gateways, Amplify and others.

Cons

The best part of AWS is also it's downfall for many indie developers and small projects - Lambda can provide great value with many of AWS services to build a full app but that requires a lot of configuration to set up - from security groups, to permissions and IAMs. Getting a lambda behind an HTTP endpoint requires a significant understanding and setup of AWS as well - API Gateways and others. That's one of the reason many devs end up going with other competitors in this space like Google's Firebase, Netlify, Vercel and others.

Another thing to consider with Lambdas is how are you going to test them? as a developer, you're going to write test and want to ensure there are no regressions but wiring up tests for Lambdas is a bit cumbersome. I don't suggest anyone to try and create local environments because you simply can't keep up with simulating all of that and mocking all of this behavior. Instead, aim to have a separate AWS account for testing and make that as close to production as you can.

Pros

Very low cost to execute functions and they have largely solved the cold start issues

Cons

Lambda is fantastic, cannot fault it. Keeps applications running at low cost.

Pros

Cost-effectiveness and ease of integration with Github pipelines and versioning make it so easy for us to deploy compute.

Cons

Not a real down-side, if run time can be increased to 30 minutes it will cover all of our payloads

Pros

It's hard to pick one feature of Lambdas that are the best since they really only have one feature: they are event driven functions that can accomplish pretty much any task that you as a developer are capable of writing. As long as you have a known input and an expected output, Lambdas allow you to do the necessary work to get you there. This setup works particularly well for creating custom APIs.

Cons

Our team has yet to find a really satisfying developer workflow. It's easy to iterate within the AWS console, but that means your code is not under version control. Once you go the version control route, you have to deal with the (self-imposed) complexity of your deployment processes. In short there feels like there's a sudden steep learning curve around best practices and code reuse, but this is a problem of many AWS services in general.

Pros

Most liked about this software is it's API integration with connectivity to database to store the important data.

Cons

Lease like is built in fault talaurance feature.

Pros

budget friendly for small to medium workload
easy to deploy using AWS CDK or terraform.
supports multiple runtimes for different programming languages
provides monitoring and logging out of the box.

Cons

cold starts can be too slow if your architecture is time sensitive.
It can get expensive for very high number of invocations.

Pros

Diverse support to runtime languages, Seamless integration with other AWS services, Heavily scalable, Execute small tasks quickly, Create functions and automate processes.

Cons

Not cost effective as every call to a function will be charged. Limited plugins and execution time.

Pros

AWS lambda is easy to use & it's highly compatible with almost all other AWS services, which makes it a clear winner in current general cloud platform. None of it's competitors come close to the mature level of this product.

Cons

It is a bit more costly than competition. Also compared to rising scalability of products like Google cloud functions, AWS lambda sometimes gets sidelined.

Alternatives Considered

Reasons for Switching to AWS Lambda

Pros

AWS Lambda is a great service offering from AWS. What I like the most is the fact that it is serverless and it allows you to write computing logic in multiple programming languages, also has the option to automate the computation.

Cons

Even though AWS Lambda is great and has great features but the online IDE is not that great and allows very limited customization. For more complex tasks we need to write our logic offline as a AWS SAML project and then deploy it to AWS. It would be great if we could install any custom package inside the online IDE itself and write more complex logic.

Pros

There isn't much you can't do with lambda once you know how to trigger and edit the scripts within. If you are familiar with python (this is what we use) then this isn't too steep of a learning curve. You are even able to front websites with lambda saving a lot of money.

Cons

The thing I would say I like least about lambda is if you have a long running job there might be some hoops you have to jump through. But every few months the execution time is getting longer and longer.

Pros

AWS Lambda offers scale that most other platforms can't and the price point is great

Cons

Super hard to configure as compared to say Twilio Functions or other serverless platforms

Pros

1. Compression on the run.
2. Scalable and still Cost Efficient
3. Platform as a Service, no need to configure underlying operation system
4. Multiple event triggering

Cons

1. Time limit on function execution.
2. Does not support editing for a file larger than 5 MB. Folder
3. No control over the environment.

Pros

AWS Lambda integrates with the entire suite of services provided by AWS, which in itself is exceptional. The tool's cost-effectiveness is also unbeatable.

Cons

The learning curve is not low compared to competitors. Generally speaking, AWS Lambda is a standard solution for numerous use cases. However, today there are many better alternatives on the market to solve specific use cases.

Alternatives Considered

Pros

triggering lambda function from more than 200 aws services
pay as you use
serverless computing
multiple programming language support

Cons

Pricing is on higher side
Have seen frequest downtime for our region

Pros

AWS Lambda is the best solution for running the development code on the server. We can take different lambda instances according to our computational requirements and size requirements.

Cons

AWS lambda is expensive compared to similar products.

Pros

Really easy to integrate and adapt to user needs

Cons

The documentation was a bit hard to navigate

Pros

The way that AWS Lambda can give you control of the way that it behaves and can be consumed is quite flexible. We were able to prepare for high-demand spikes on the services with hot availability, as well as connect them to be triggered by different events. This last part allowed them to be flexible for many patterns in our services as front and middle actuators in the flow of data.

Cons

This service is simple to use, so I can't recall a negative feeling associated with it.

Alternatives Considered

Reasons for Switching to AWS Lambda

Pros

Easy, simple and powerful for data processing. Highly integrated with different AWS services. Very powerful for event driven architecture.

Cons

AWS lambda timeout is 15 mins. For long running process AWS lambda is not suitable.

Pros

Lambda automatically scales up or down based on the number of incoming requests.

Cons

it has some limitations and challenges that can be frustrating, especially for large-scale or complex applications

Pros

Super easy to use and set up, you really don't need to know a lot to get your code running in the cloud, and the best part of it is that it will scale to very very large without anything on your side.

Cons

In large scales, you need to know a little about lambda in order to make sure your service runs without any disruptions.

Pros

First best thing about AWS lambda is that provide serverless architecture that means there is no need to manage server and architecture all these things are handle by AWS lambda

Cons

One bad thing about AWS lambda is that when you call or invoke the function first time or after period of time then its take too much time to execute.

Pros

It allows you to run code without provisioning or managing server.You have to pay for only compute time for which we have used the service.Many of the automations are possible by using lambda function

Cons

sometime the execution time and memory,may be limitations.Monitoring is little bit complicated at some extent.

Pros

Super flexible with the whole gamut of AWS tools to support if needed. The free tier allocation is fantastic, and general pricing is very competitive.

Cons

None. It's the best option for cloud functions.

Pros

I can create a simple lambda function in minutes. The deployment process is pretty easy to automate.

Cons

For python applications, the dependencies management is a bit hard.

Pros

It a serverless application typepay when usedit is triggered only when events happenVery easy to use and implementcan be integrate with other applicationssupport several coding languagesused dailyi am personally using it to ingest cloudwatch logs to new relic

Cons

There is nothing to really dislike about lambda

Pros

The pricing of AWS Lambda is reasonable, and I like that I can activate and deactivate the service without deleting the project. Also, I like that I can use AWS Lambda in the AI project lifecycle to manage the pipeline and connect the model to up for deployment.

Cons

The documentations available for AWS Lambda on AWS are very limited and do not provide an implementation to an end-to-end project. Also, I do not like the limited control over the infrastructure as AWS Lambda does not allow me to control this point.

Pros

A meticulously designed serverless architecture.Exceptional service availability.Proficient Python comprehension.Seamless team adaptability.Abundant features for seamless integration with RDS, S3, and various other AWS services.

Cons

- Low monitoring capability- Few documentation to set AWS CloudWatch- Feature CLI is too hard to set because each detail declaration is concerned to functions

Pros

Serverless and easy to deploy. In combination with AWS secret manager to implement microservice for RESTFul APIs

Cons

Dependencies and quite complicated to deploy and manage using API Gateway.

Pros

I like the developer interface and the fact that there are no servers to upkeep.

Cons

If you need high speed execution, there might be limitations.

Pros

Using AWS lambdas provides an excellent win from the perspective of development velocity and removing the complexity around deployment and maintaining infrastructure. It allows developers to focus on the actual business logic of the services/processes instead of the tools being used. It should be noted, that this also reduces the number of places where things are likely to go wrong which is an underappreciated benefit.

Cons

This is quite expensive compared to a service/process you create and manage from the ground up. In the long run, you'll likely either find yourself moving away from using lambdas, or constantly redesigning your architecture to reduce the cost while servicing more throughput/complex logic. That is probably true for most software tools, but lambda processing costs can grow quite unexpectedly. Beware of memory demands - that can quickly add up and otherwise crash your lambdas (semi quietly) in the background.

Pros

I think the biggest pro of AWS lambda itself is that is an AWS service, this makes integrating other AWS services straightforward, SQS, SNS, Dynamodb, Appsync, APIGateway, IAM, to name a few, are some of the services I had a really pleasant experience to integrate with.

Another Pro I would say is the ease of development, you can write your code in either Java, Node.js, Python or Go and deploy it easily using CDK or Serverless framework.

The pricing is also very attractive, you are only charged for the time your code is running and the amount of memory you use although its a little bit pricey compared to other solutions like firebase functions or cloudfare workers.

Cons

The biggest cons I have noticed when using lambdas are:

- Cold starts: when your function is not already running in memory and needs to be spun up, this can take a few seconds and during this time your function is not available, really discouraging the development of lambda functions in JVM languages or others that have a big runtime

- Observability: while it's true that you have logs out of the box in AWS Cloudwatch/CloudTrail and Xray metrics, observability is not the greatest, for instance log text search is not something you get. Usually this is solved by adding another provider like ELK stack or Lumigo.

- Vendor lock-in(if applies) : Taking advantage of all the benefits of running functions on AWS may not be the greatest idea when you care about vendor lock-in and you are looking for a cloud agnostic solution this would have an impact also in pricing as AWS is not the cheapest cloud provider.

Pros

We like how Lambda is able to be deployed and updated quickly. It allows us to spend less time worrying about server loads or accessibility knowing that it is on the cloud and reliable.

Also the benefits of being ingrained in the AWS infrastructure is helpful with connecting to our other services.

Cons

I think the console aspects of the software could use improvements. Here are some examples:
1. The testing UI is basic. You can create test cases, but in doing so you can't even view the codebase unless you click off. I would like to be able to look at both at the same time.
2. The code editor could use some enhanced functionality of popular editors like VSCode or even google docs. Specifically, one thing I noticed is I cant do CTRL+} with several lines highlighted to tab all lines over.
3. Lambda Layers are helpful but I would like to be able to view the code inline somehow rather than just see the version of the layer i am using. It would make it easier to differentiate when your lambda layer has several dozen versions, which version I am using or need.

Pros

It is easy to get started, within a couple of steps you will be able to run a highly scalable solution with API gateway and lambda. It is good for running small scripts that can complete within 15 minutes. Their documentation for this service is comprehensive, provides good examples for the developers. It is completely serverless, no extra effort needed to manage servers.

Cons

It gets complicated very quickly if you are using it for complex tasks like stream processing. There are some performance issues that you might encounter due to cold starts, hence keeping lambda warm is very essential. Debugging the issues through cloudwatch logs in a time-based manner can get challenging if your lambda is getting invoked multiple times in a short duration. The maximum code runtime is for 15 minutes and after that, your lambda will get timed out, so if your code has a runtime of greater than 15 minutes, you need to move to other AWS solutions like ECS fargate.

Pros

1. I like how I'm able to implement lambda functions with various languages of my choosing whether its Python, Java, Go, Powershell, Ruby or Node.js

2. I effectively save cost by using lambda for my deployments as I pay for the computation time during which my lambda function is running.

3. Since its serveless architecture, I don't have to worry about the underlying infrastructure or its maintenance.

4. It gives me event-based trigger which eases my deployments as it enables automated procedure based on my lambda functions.

5. It is helpful to perform various operations and resource administration activities like monitoring resource status, updating security patches, deploying applications, etc.

Cons

I didn't find anything to like as least abut AWS Lambda. One thing to mention is, the TTL for each lambda is 15mins so after that period so if its customizable means we will be able to do more deployments running a single lambda function.

Pros

It scales unendingly. We picked AWS's serverless engineering explicitly for its capacity to begin little and scale on a case by case basis. Short computational code - For those that need adaptability without keeping up with servers, AWS lambda essentially accomplishes all of this as one help.
Versatility - For most lambda administrations, you are charged by run sum, insofar as run-time stays low.

Cons

It continually changes starting with one case then onto the next, so there is zero power over the execution climate. A Lambda based work process can be more complicated to investigate in light of the relative multitude of various capacities that might be called because of your work process.

Pros

Every script uploaded into Lambda can be attached to an automatic trigger and an API Gateway endpoint. This could save a very important amount of memory usage for certains applications because the processing is made by AWS. It offers the convenient possibility of hosting your app in a Bitbucket or to upload it directly as a zip, saving a lot of time in complex deployments.

Cons

There are not cons regarding this service. It does what offers, a fast and very reliable server-less service that can execute scripts in parallel than your apps.

Pros

Its serverless, servers are not running up all the time, they run only when triggered.Its cheap, you need to pay only for what you have used.Its fastest, it does the computing a way faster than the other virtual servers.Its easy to use with lots of Integration plugins available.

Cons

The only con is number of concurrent runs is very less i.e. under 1000.For heavy applications we need more number of concurrent runs.

Pros

We have decided to use AWS Lambda to move some of the workload out of the servers that were not used often to process some of the workloads. I have never worked with Serverless approaches before, so AWS Lambda was my introduction to serverless world.

AWS Lambda provides API in several programming languages, so it was very easy to jump straight into implementation and write some functions. It turned out to save a lot of money, because we could stop the server that was used sparsely. AWS Lambda has consumption based model so it was very cheap and superb effective.

Cons

I did not find any cons. Obviously it is not possible to write big services with AWS Lambda but some of the workload can be easily moved to Lambda to save on costs and maintenance.

Pros

development will easy when we can do from console, this tools menu have powerfull tools for development

Cons

some of the command need to have time for this role apply.

Pros

AWS Lambda provides the capability to deploy and use serverless functions in a handful of programming languages, with many useful integrations with other AWS services. It enabled us to meet our performance benchmarks for large-scale applications right out of the box due to its capability for a high level of concurrency, and the integrations with AWS SQS and AWS API Gateway were particularly useful for our use cases.

Cons

The inherent limits set on the size of the function and the requirement of packaging dependencies along with function code has proven to be difficult at times, although these problems can be alleviated by using layers and Lambda Containers.

Pros

Lambdas support multiple languages and have clients for major AWS Tools like Opensearch, DynamoDB, SQS etc.

Cons

Lambda cold start is a major pain point. There have been multiple solutions given for this previously, but none of them have been satisfactory.