Backend Admin Panel like Django's
Unanswered
Asiatic Lion posted this in #help-forum
Asiatic LionOP
All this while I was under the impression to use NextJS as an SPA only and use a backend like Django.
But recently when I went through one NextJS + SupaBase course, I realized that NextJS is being used for backend also in nodeJS.
I choose Django only for its free backend admin panel. If going via the NextJS server-side route, then what can I use as a backend panel ?
But recently when I went through one NextJS + SupaBase course, I realized that NextJS is being used for backend also in nodeJS.
I choose Django only for its free backend admin panel. If going via the NextJS server-side route, then what can I use as a backend panel ?
8 Replies
there's nothing out of box
you have to build your own
Asiatic LionOP
But does it make sense to create a project use a NextJS + Django tech stack ?
yea
I've done it a few times
Asiatic LionOP
So you choose Django over NextJS's nodeJS for server-side tech ?
@Asiatic Lion So you choose Django over NextJS's nodeJS for server-side tech ?
it depends on what I wanna build tbh.
If I wanna quickly scaffold stuff and get it out in the wild, I use nextjs as Fullstack
but if I want to also expose public APIs for myself or public to consume, I use a dedicated backend stack or sometimes just add hono/elysia to nextjs itself
If I wanna quickly scaffold stuff and get it out in the wild, I use nextjs as Fullstack
but if I want to also expose public APIs for myself or public to consume, I use a dedicated backend stack or sometimes just add hono/elysia to nextjs itself
Yellow-billed Magpie
Yes , Nextjs is a nice metaframework because it gives you a full nodejs environment, you can definitely setup a Full Stack Application and code the whole backend in nextjs, but the benefits of having a different server with the backing service always exists.
I like to think of nextjs as the 'transformer' backend and an actual backend framework service as the actual API provider, and let nextjs node runtime communicate with the backend service separately. So that I can have the logic separated. So yea go ahead and setup a separate backend if you want.
I like to think of nextjs as the 'transformer' backend and an actual backend framework service as the actual API provider, and let nextjs node runtime communicate with the backend service separately. So that I can have the logic separated. So yea go ahead and setup a separate backend if you want.