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 choose eight out of ten because to go ahead with Serverless, we need to do YAML file creation and other format file creation. So it might not be having the idea. That is the only thing that I observed.
Product Manager at a tech vendor with 10,001+ employees
Real User
Top 10
Dec 2, 2025
I do not have any specific suggestion at this point on how Serverless can be improved for my use case. Perhaps down the line I will have more information. The reason I choose a seven is primarily resource-based scheduling. This is what we are not able to get around on Serverless. It solves a main use case, but it still does not solve our batch executing and batch simulation use cases. However, if this could be one solution to move away from a traditional HPC scheduler, I would have definitely given a ten.
Serverless revolutionizes application architecture by eliminating the need for server management, offering a scalable, cost-efficient approach for modern development needs. It enables developers to focus on writing code without the complexities of infrastructure handling.Originally designed for enhancing agility, Serverless provides on-demand function execution, ensuring seamless scalability and rapid deployment. As a back-end architecture, it allows businesses to execute code in response to...
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 choose eight out of ten because to go ahead with Serverless, we need to do YAML file creation and other format file creation. So it might not be having the idea. That is the only thing that I observed.
I do not have any specific suggestion at this point on how Serverless can be improved for my use case. Perhaps down the line I will have more information. The reason I choose a seven is primarily resource-based scheduling. This is what we are not able to get around on Serverless. It solves a main use case, but it still does not solve our batch executing and batch simulation use cases. However, if this could be one solution to move away from a traditional HPC scheduler, I would have definitely given a ten.