🚀 Question about using an external backend with Next.js App Router
Unanswered
European pilchard posted this in #help-forum
European pilchardOP
Hi all! I’m building a custom admin dashboard using Next.js 15 with the App Router, Server Actions, and Auth.js — so far, authentication has been working well.
However, as my project grows, I’m starting to feel that I'm reimplementing backend features that are already well-handled in frameworks like Laravel, especially when it comes to:
File validation and handling (e.g. uploading multiple images related to portfolios)
General backend structure (like how Laravel handles requests, validation, authorization, etc.)
I'm concerned that if I keep building everything in Next.js, I might hit a wall where quality, maintainability, and security are harder to guarantee — compared to using a dedicated backend framework.
So my questions are:
Do others here also feel limited by Next.js for backend-heavy logic?
Would using something like Laravel as an external API backend be a smart move?
And are there large companies that also use Next.js only as frontend or BFF, combined with stronger backend stacks like Java/Spring, Rails, etc.?
Thanks in advance for any insight — just trying to make the right long-term architectural decision!
However, as my project grows, I’m starting to feel that I'm reimplementing backend features that are already well-handled in frameworks like Laravel, especially when it comes to:
File validation and handling (e.g. uploading multiple images related to portfolios)
General backend structure (like how Laravel handles requests, validation, authorization, etc.)
I'm concerned that if I keep building everything in Next.js, I might hit a wall where quality, maintainability, and security are harder to guarantee — compared to using a dedicated backend framework.
So my questions are:
Do others here also feel limited by Next.js for backend-heavy logic?
Would using something like Laravel as an external API backend be a smart move?
And are there large companies that also use Next.js only as frontend or BFF, combined with stronger backend stacks like Java/Spring, Rails, etc.?
Thanks in advance for any insight — just trying to make the right long-term architectural decision!
1 Reply
West African Lion
I know that the Nextjs /api was not built as a workaround, but probably the best to do when dealing with really complex business (or not) logic, is to having a dedicated backend.
We need to remember that these are all tools, and we should choose the correct one for each scenario... If the option to use nextjs is just because of its built-in backend, I think that's not the best decision
We need to remember that these are all tools, and we should choose the correct one for each scenario... If the option to use nextjs is just because of its built-in backend, I think that's not the best decision