Serverless Framework

Serverless stands out for easy deployment without any server hassle, and if we need scalability or efficiency, the Serverless framework is mostly cost-efficient because we integrated a Lambda function that charts user request steps, which is why it is cost-efficient. We do not need any high-profile developer for maintaining a server, which is the good thing about Serverless.

Serverless positively impacts my organization by saving time since we do not deal with deployment hassles, and Serverless costs less than other server maintenance options. The positive impact of Serverless is its ability to reduce the number of people needed for project deployment. As a software engineer working on DevOps for project deployment, I find that without Serverless, every project needs multiple workers, but I can handle both development and deployment easily, which reduces hassles for software.

My advice for developers considering using Serverless is that if they face any hassle with deployment, they can easily choose Serverless for automation, coding, and deployment, as well as local setup and project deployment in any server automatically.

Serverless is a great tool for every software engineer, and if any software engineer has not used this tool, they are lacking knowledge and a great opportunity. I tell every software engineer that if they have not used Serverless, it is important for every developer at some point to experience it. I give this review a rating of 9.

My main use case for Serverless  in my last company involved using Lambda and the AWS Fargate  service, and for my current organization, we are migrating some services to Serverless .

A specific example of how I used Serverless in one of my projects is when my last company, a product-based company, had to test our product on a microservice level. On that occasion, we used the EKS Fargate service to conduct short-term testing.

Regarding my main use case for Serverless, we have also set some alert alarms on AWS  for compliance breaches, which trigger Serverless to execute scripts or actions.

Serverless offers the best features including automatically scaling resources based on requirements, such as needing only one core and two gigabytes of RAM, making it cost-saving, especially in terms of FinOps where we focus on saving company costs without needing to specify any hardware.

Serverless positively impacts my organization by being really cost-effective and serving as a production performance testing tool. As we increase the load, it automatically increases the CPUs and RAM without needing any manual intervention or heavy servers for this type of testing.

I have seen specific outcomes where we set compliance parameters, providing only two cores and four gigabytes of RAM for testing. If anyone uses more than four or eight, our Serverless Lambda function gets triggered, causing Serverless to take action to reduce those specifications.

Serverless can be improved by making it available across all cloud platforms. Implementing it in a local environment would be really helpful as well, since outside of Kubernetes  and OpenShift, it is not a proper example of Serverless.

I have been using Serverless for around five or more years.

Serverless is stable most of the time, though we occasionally face issues, but that is primarily due to our usage of the public cloud.

Scalability of Serverless depends on our specific use case. If the code requires more CPU or RAM, Serverless automatically provides it. For instance, when I launch an app using Serverless and the load increases, the necessary CPU and RAM scale automatically without requiring any additional configuration from me.

Customer support from AWS  is marvelous.

Previously, I used Kubernetes  and OpenShift as production solutions before switching to Serverless for staging.

My experience with pricing, setup cost, and licensing for Serverless spans around five or more years.

I have seen a return on investment since, as I mentioned, it is a product-based tool that minimizes human effort. We do not need to approach the infrastructure team for specific testing resources, as developers and testers can directly load code, test, fetch results, and set up production environments based on those results.

I did not evaluate other options before choosing Serverless. In production, we use Kubernetes, while for staging and development, we see the advantages of using Serverless for small use cases, and for larger applications, we revert to Kubernetes.

I would rate Serverless a seven out of ten for testing. Serverless is not suited for production environments. It is designed for stage, testing, or development environments, while we use Kubernetes, OpenShift, and several other tools for production deployments. My advice for others looking into using Serverless is to be very careful. If we create a loop in the code, it can require thousands of CPUs and RAM, which could cost much more than expected, so writing the code requires careful consideration when using Serverless.

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.

My main use case for Serverless  is developing full stack applications and APIs.

The best features Serverless  offers is the ease of going to market. It is easy to simply go and deploy your code. You just focus on the functionality while the infrastructure is already set up there, so I do not have to spend hours setting up the infrastructure.

Serverless is easy to start with, especially for features like minimum viable products. If I want to develop a full set of applications and go to market immediately, then I prefer Serverless. Also, if you want to scale up, then Serverless is the best way. It is scalable and more secure, and it is on-demand, so it is easy to reduce or increase the load based on our needs. It is automated and very cost-effective. We are not billed per second like with provisioned services. Serverless offers a great pay-as-you-go model that is really excellent. It also has very good integration with all services from front-end to back-end, following a microservices concept. I love this concept and the supporting features including X-ray to find any issues in terms of failures, or CloudWatch to gather logs. It is an amazing set of components and microservices working together to provide solutions to single problems.

The most important feature is time-saving. When we have an idea and want to test it, we need to go to market quickly. Developing and deploying the MVP to check the idea is really a time-saving approach that has impacted our organization.

Almost 60% of time was saved when we considered Serverless. Because we always had to wait for server provisioning and other provisions if we wanted to do something else or pursue other projects using non-serverless methods. But in Serverless, the infrastructure is already set up, so we just need to go and deploy and start using it. We almost saved 60% of time. Cost-wise, we also saved a lot of money by not buying provisions and not paying for idle time. In Serverless, there is no need to pay for idle time. That is the core advantage of using Serverless.

Serverless can be improved with more usage videos. I found a lot of online tutorials using Serverless, but it could have more use cases with more detailed videos. For example, videos on DynamoDB single-table design and how to develop efficiently would be helpful. Additionally, detailed content on how to improve Lambda debugging and comprehensive documentation would be helpful for developers.

I have been using Serverless for the last four to five years.

I can provide details of a recent project called Project Creative Gifts, which I developed fully with AWS  Serverless technology. It is an online gift e-commerce store developed using Angular as the front-end and Node, NestJS as the back-end. The complete solution is deployed in Serverless on AWS . I used various Serverless technologies and tools to deploy this application. For the front-end, I used S3  bucket web hosting and CloudFront as a CDN . For the back-end deployment, I used API Gateway, Lambda, and DynamoDB. For authentication purposes, I used Cognito to authenticate the users.

It is an e-commerce online store with a lot of access points to store and retrieve data. I considered various options to save money and keep a single table design. I conducted a lot of research and created multiple access points to securely store and retrieve data in a more effective and cost-effective manner while maintaining performance. This presented a challenge, but I finally  managed to solve it by placing the design appropriately.

So far, I am satisfied with Serverless. Everything is integrated and everything is set up perfectly. I would rate this review an eight out of ten.