Seperate or external back-end
Is it good having a seperate back-end using e.g. Django and communicating with api, or is it best practice for Next to use something like Prisma?
10 Replies
django is for api's?
prisma is not the same as django
this qusetion is so confusing, you gotta rewrite it or make it make more sense lol
But for like the database stuff
django has nothing to do with database stuff
or it does but it does a lot more
Let me rewrite it in a few minutes haha
Alright this is my current situation
I'd like to experiment with building apps with Next. I'm familiar with React and a little with Next, but so far I have zero experience with Next's backend capabilities
I was wondering if I should/could use an external back-end and communicate to my front-end Nextjs, or is this a bad approach and should I dive into Next's back-end and use something like Prisma for a database
At work we have several projects with NextJS and then a back-end/middleware with either Django or a PHP framework
Hence my question
@barry
Alright, yes I would definitely dive into the backend aspect of Next.js since it's awesome, you can pop up end points smooth like butter in no time, even type safe with tRPC.
Sorry for the earlier confusion haha
Would I need something like Express?
No just look into the docs.
See how it works
@Niels Have you looked anything at tRPC?
I would strongly suggest you take a look at that as well 😄
Then you can get full type safety between BE and FE without any code gen
Been trying to get an idea of it, couldn't really find a clear example on tRPC thus far
The t3 default template.
The TLDR of you not knowing what to do and what to do about it is:
Just begin making stuff. Quantity over quality is right at this point. Just use stuff, learn new tech, get your own opinion, instead of researching for hours and hours to make 1 thing.