All good stuff until it’s not.
Next.js is fantastic yet we faced some issues with it.
1) if you host with Vercel all is fantastic until you start getting sky high bills. You can self host then but the migration can be costly
2) when self hosting memory leaks has been a major issue for us
next.js cache is leaky under certain circumstances;
undock was leaky and it cost us days to find proper node version
SSR can be leaky
We have leaks on and off between releases and frankly stopped trying to isolate them just waiting until server is rebooted.
Vercel devs doesn’t care about those leaks on GitHub discussions - maybe because they are paid by their hosting services which accrue extra $$ when memory leaks :)
I wonder what supabase bill would be for a relatively successful project. I ended up running away from Firebase to full blown GCP setup after years of pain
Nest.js is sleek yet you need a comparatively high level of experience to work with it properly. And it’s pretty slow among Node.js frameworks- one of the slowest in fact. But lots of good features
I wonder what is your experience with running projects on this tech stack in Production and what hosting setups you used and what bills your clients had to foot .
I always prefer relational databases (postgres) over document databases for most tasks. They are not always the best, but they usually are. Depending on your application, most of the time you are connecting pieces of data in an organized manner, this can get more complicated with Mongo, especially if you aren't very strict with on you build the documents.
Thanks for sharing your thoughts!
Regarding NextJs, we’ve been running it in Docker on a VM (4-16gb of ram dpanding on the project), and it’s been working really well for us, except for occasional quirks. Since we don’t have SSR-heavy applications, it handles up to 200–300 concurrent users reliably.
As for Supabase, their $25 subscription covers most of our projects, and when we exceed that, we migrate to a self-hosted instance with Docker. The migration process is seamless, thanks to their detailed documentation.
For NestJS, we only use it when we have a backend team of 3+ developers. Frameworks like Express or Deno can offer too much flexibility, which often leads to messy codebases without strict team coordination. NestJS provides the structure and scalability we need for larger, more organized teams.
1) I didn't know you can migrate Supabase to a self-hosted instance (I never used it to be honest). Thanks for the tip.
2) For Next.JS we use much smaller RAM for VM and we're heavy on SSR due to the nature of our projects. What hosting did you use for it?
3) Express/Koa just need proper guardrails and code review. But I agree that NestJS offers some built-in guardrails which allow less code drift between team-members.
I agree with Nextjs not being all it's pent up to be. I at least respect the article for confining it to the frontend box. You would have to be some sort of glutton for punishment to use Nextjs as your backend.
For the backend, NestJS is alright but there are way faster, simpler, yet just as full featured NodeJS backend frameworks. I would even rather choose Deno2 over NestJS for a backend if I were to start something right now.
Anything light that prioritizes Typescript and can generate some sort of contract from your backend code that can be used by all language-agnostic clients and micro-services alike, especially on a code-intellisense level.
By contract, I mean the OpenAPI/swagger (rest), GraphQL or gRPC (protobuf) type specs.
Personally, I prefer openApi/swagger contracts for most general APIs. There are a lot of lightweight frameworks that meet this requirement. Given the rate of creation of new NodeJS frameworks, I want this post to stand the test of time by not listing anything specific here 😂... otherwise I would have mentioned a NodeJS framework I built myself.
No one can really answer that question for you without more information. Postgres is generally a safer bet if you don't know what your project could become, because it can also double as an indexable document database similar to mongodb thanks to JSON/JSONB
Some comments have been hidden by the post's author - find out more
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.
All good stuff until it’s not.
Next.js is fantastic yet we faced some issues with it.
1) if you host with Vercel all is fantastic until you start getting sky high bills. You can self host then but the migration can be costly
2) when self hosting memory leaks has been a major issue for us
I wonder what supabase bill would be for a relatively successful project. I ended up running away from Firebase to full blown GCP setup after years of pain
Nest.js is sleek yet you need a comparatively high level of experience to work with it properly. And it’s pretty slow among Node.js frameworks- one of the slowest in fact. But lots of good features
I wonder what is your experience with running projects on this tech stack in Production and what hosting setups you used and what bills your clients had to foot .
what's your take on the MERN stack ? and about the database ... which is better to use mysql/postgres or mongo db ?
I always prefer relational databases (postgres) over document databases for most tasks. They are not always the best, but they usually are. Depending on your application, most of the time you are connecting pieces of data in an organized manner, this can get more complicated with Mongo, especially if you aren't very strict with on you build the documents.
Thanks for sharing your thoughts!
Regarding NextJs, we’ve been running it in Docker on a VM (4-16gb of ram dpanding on the project), and it’s been working really well for us, except for occasional quirks. Since we don’t have SSR-heavy applications, it handles up to 200–300 concurrent users reliably.
As for Supabase, their $25 subscription covers most of our projects, and when we exceed that, we migrate to a self-hosted instance with Docker. The migration process is seamless, thanks to their detailed documentation.
For NestJS, we only use it when we have a backend team of 3+ developers. Frameworks like Express or Deno can offer too much flexibility, which often leads to messy codebases without strict team coordination. NestJS provides the structure and scalability we need for larger, more organized teams.
1) I didn't know you can migrate Supabase to a self-hosted instance (I never used it to be honest). Thanks for the tip.
2) For Next.JS we use much smaller RAM for VM and we're heavy on SSR due to the nature of our projects. What hosting did you use for it?
3) Express/Koa just need proper guardrails and code review. But I agree that NestJS offers some built-in guardrails which allow less code drift between team-members.
Supabase is just hosted postgres right ?
They try to be more than that. You can also self-host supabase.
But I didn't try the thing at all so cannot judge
I agree with Nextjs not being all it's pent up to be. I at least respect the article for confining it to the frontend box. You would have to be some sort of glutton for punishment to use Nextjs as your backend.
For the backend, NestJS is alright but there are way faster, simpler, yet just as full featured NodeJS backend frameworks. I would even rather choose Deno2 over NestJS for a backend if I were to start something right now.
what Node.js frameworks would you choose if not Deno or Nest?
Anything light that prioritizes Typescript and can generate some sort of contract from your backend code that can be used by all language-agnostic clients and micro-services alike, especially on a code-intellisense level.
By contract, I mean the OpenAPI/swagger (rest), GraphQL or gRPC (protobuf) type specs.
Personally, I prefer openApi/swagger contracts for most general APIs. There are a lot of lightweight frameworks that meet this requirement. Given the rate of creation of new NodeJS frameworks, I want this post to stand the test of time by not listing anything specific here 😂... otherwise I would have mentioned a NodeJS framework I built myself.
what's your take on the MERN stack ? and about the database ... which is better to use mysql/postgres or mongo db ?
No one can really answer that question for you without more information. Postgres is generally a safer bet if you don't know what your project could become, because it can also double as an indexable document database similar to mongodb thanks to JSON/JSONB