NextJs Manage API Approach
Unanswered
Manav Verma posted this in #help-forum
hi! In nextjs app
i tried many approaches to arrange api's
(Note: i am using laravel as backend and Nextjs 15 app directory for frontend)
I have used these approaches
api folder (default) - but this has overhead of writing more code
directly add full fetch where i need (fetch with url att the same code) - causes not to follow dry rule
also tried action.ts approach - eg: blog/blog-action.ts is located there
if i need blog api from blog/action.ts. then i need to call from that path (i personally don't like this approach)
create seperate folder (which has api's defined (axios) like blogApi.ts, categoryApi.ts etc..)
which i should follow and what will be good?
the websites that i create has alot of api's
also i need to focus on easy scability for future.
What should i follow?
Is there's any better approach than this? need suggestions
i tried many approaches to arrange api's
(Note: i am using laravel as backend and Nextjs 15 app directory for frontend)
I have used these approaches
api folder (default) - but this has overhead of writing more code
directly add full fetch where i need (fetch with url att the same code) - causes not to follow dry rule
also tried action.ts approach - eg: blog/blog-action.ts is located there
if i need blog api from blog/action.ts. then i need to call from that path (i personally don't like this approach)
create seperate folder (which has api's defined (axios) like blogApi.ts, categoryApi.ts etc..)
which i should follow and what will be good?
the websites that i create has alot of api's
also i need to focus on easy scability for future.
What should i follow?
Is there's any better approach than this? need suggestions
1 Reply
@Manav Verma hi! In nextjs app
i tried many approaches to arrange api's
(Note: i am using laravel as backend and Nextjs 15 app directory for frontend)
I have used these approaches
api folder (default) - but this has overhead of writing more code
directly add full fetch where i need (fetch with url att the same code) - causes not to follow dry rule
also tried action.ts approach - eg: blog/blog-action.ts is located there
if i need blog api from blog/action.ts. then i need to call from that path (i personally don't like this approach)
create seperate folder (which has api's defined (axios) like blogApi.ts, categoryApi.ts etc..)
which i should follow and what will be good?
the websites that i create has alot of api's
also i need to focus on easy scability for future.
What should i follow?
Is there's any better approach than this? need suggestions
if you have your project as a monolith or monorepo you can use laravel as an API in next.js in a very simple way.
What you need to do is configure a rewriter in next.config.ts so that the API routes are form the laravel server.
This way all the server logic would be outside the next project and in it you would only handle the responses.
https://nextjs.org/docs/app/api-reference/config/next-config-js/rewrites
What you need to do is configure a rewriter in next.config.ts so that the API routes are form the laravel server.
This way all the server logic would be outside the next project and in it you would only handle the responses.
https://nextjs.org/docs/app/api-reference/config/next-config-js/rewrites