Is Next.js 14 on Vercel Enough for Scalable API Services, or Should I Use Nest.js for Backend?
Unanswered
Miniature Schnauzer posted this in #help-forum
Miniature SchnauzerOP
I'm currently using Next.js 14 to handle both the frontend and backend of my project, hosted entirely on Vercel. The backend serves APIs for tasks like analyzing CVs, integrating with other APIs, and returning JSON data, and it’s working well so far.
However, as I plan to scale and sell my API as a service, I’m also considering requirements like:
- API key management and distribution
- Rate limiting and more complex business logic
- Scalability and performance optimization
My main question is:
Is it a good idea to rely solely on Next.js 14 (hosted on Vercel) to handle these backend requirements at scale, or should I consider using Nest.js as a separate backend service for better handling of API management, security, and scalability?
I'd appreciate insights from anyone who has scaled API services with either framework, especially when planning for commercial API distribution.
However, as I plan to scale and sell my API as a service, I’m also considering requirements like:
- API key management and distribution
- Rate limiting and more complex business logic
- Scalability and performance optimization
My main question is:
Is it a good idea to rely solely on Next.js 14 (hosted on Vercel) to handle these backend requirements at scale, or should I consider using Nest.js as a separate backend service for better handling of API management, security, and scalability?
I'd appreciate insights from anyone who has scaled API services with either framework, especially when planning for commercial API distribution.
2 Replies
Rainbow trout
This is completely fine. If you have any long running tasks, you should consider a seperate backend for this task since it's getting expensive really quick on serverless.
Sun bear
I guess you need to separate backend service for better handling of API management , security.