As far as switching goes, most of the time I did it in the framework itself. NextJS offers the ability to create API routes that run as serverless functions but only if you deploy the app on the Vercel platform. Gatsby does the same thing now. You can incrementally migrate to serverless pretty easily depending on the complexity of your API and the size of your team. For me, it was pretty easy since my apps are simple and I have a lot of DevOps experience.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Oh, here you mention really interesting thing. How easy or difficult was to switch to serverless from regular on-server api development?
As far as NestJS goes, it's very easy to use it for serverless since they have Standalone applications. docs.nestjs.com/faq/serverless
docs.nestjs.com/standalone-applica...
As far as switching goes, most of the time I did it in the framework itself. NextJS offers the ability to create API routes that run as serverless functions but only if you deploy the app on the Vercel platform. Gatsby does the same thing now. You can incrementally migrate to serverless pretty easily depending on the complexity of your API and the size of your team. For me, it was pretty easy since my apps are simple and I have a lot of DevOps experience.