Serverless Reviews

My main use case for Serverless is hosting applications and running code.

I can provide a specific example of how I'm using Serverless for stream applications or running code: I am running applications without servers, executing ad hoc tasks, Lambda tasks, or function tasks.

I have additional context about my main use case with Serverless. We did not want to host servers and pay for idle servers just to run code and ad hoc tasks, so we switched to Serverless. We now only pay for the amount of time we are running applications or the amount of time we are using the application.

Serverless has positively impacted my organization, and we are seeing a positive response in terms of pricing and scalability.

Serverless offers valuable features including ad hoc task execution, event-based triggers, integration with other features, other functions, and other applications.

The integration with other features and applications has particularly helped me. When something arrives in my S3 bucket or any other source, it triggers an event and runs Serverless applications to execute tasks.

Serverless can be improved with more stability, more scalability, and more integration with other applications.

There are improvements needed around triggers and event-based functionality. Sometimes we see old results instead of new results when events trigger. This area requires improvement.

I rate Serverless an eight because it can be improved in stability. Sometimes we see older results, and sometimes it doesn't trigger based on the event. Additionally, sometimes we get charged more money than we actually use, so these areas require improvement.

I have been using Serverless for two to three years.

Serverless is stable, but it can be improved.

Serverless can scale on demand.

Serverless customer support is good.

We have not used any other solution before this.

My experience with pricing, setup cost, and licensing demonstrates that pricing is good because we only get charged for the amount of time we use and the amount of time we trigger events. Setup cost is minimal because it is easy to use. It requires only some code, which is why it is easy to set up.

I have seen a return on investment. Money and time are saved, and it is deployed in a public cloud on AWS.

We have not evaluated any other option before choosing Serverless.

My advice to others looking into using Serverless is that you can use it if you want to save money, if you don't want to manage servers, if you only want to be charged for the amount of time you use, and if you want to run code and ad hoc tasks. Serverless offers great scalability. I rate this product an eight.

Our main use case for Serverless is to build Serverless APIs, and the complete back-end is built with Serverless. A specific example of an API or back-end workflow built using Serverless is a parts integration related to buying parts catalogs, which is a third-party integration API, and everything was built using Serverless.

Serverless offers the ability to test locally, as it can spin up a bunch of AWS resources and mock them as if they were deployed onto the cloud, allowing development locally without having to spin up the resources into an actual AWS account.

The local testing feature has helped speed up development for my team without having to wait for deployment into the cloud, and for debugging purposes, it has been beneficial to find out when things are not working properly as I can step through the code and see or log local errors.

Serverless has positively impacted my organization as it has been a good experience for the team overall because it is a new framework that we had to learn, and cost-wise, it helps because moving to Serverless means you do not have resources spinning all the time. It only uses Lambdas, and it is infinitely scalable, so you only use resources as the quota is used up or as the Lambda is invoked, with team collaboration being mostly about everyone learning something new together and giving each other tips.

I struggled with wanting to put breakpoints throughout the code and then use the debugger. At the time, I was not able to step through the code with breakpoints, so if Serverless had that support, that would be great.

The overall documentation is great, and I do not have anything else to add about needed improvements.

I have been using Serverless for about a year and a half.

Serverless is very stable.

Our customer support experience has been straightforward as we have not really had to contact them.

Previously, we had a .NET Core back-end deployed onto ECS clusters, but when we switched over to Serverless, there is less DevOps involvement, and we take all the AWS resources we need, while Serverless helps deploy everything.

My experience with pricing, setup cost, and licensing was all very straightforward and very easy to use.

I have seen a return on investment in terms of time saved. To be honest, we were using .NET as our back-end for the most part, but switching over to use Serverless made the development cycle a little bit faster, as we use one-week sprints rather than two with .NET.

Before choosing Serverless, we evaluated other options, including AWS SAM, but it was mostly just between these two options.

Our customer support experience has been straightforward as we have not really had to contact them. I would rate this review an 8.