Hi, I suggest to start with everything in next and if your project takes off and you need to scale, then you can start thinking of adding extra complexity with a separate backend.

I do recommend T3-stack, you get a lot for free, like authentication.

for auth you recommend next auth or prisma? i have all in mysql

planetscale uses ssl

Prisma doesn't deal with authentication, just as an ORM for your database

As @Polar bear mentioned, at the very begening of your fullstack journey, using api folder and serverless functions will help you to start your project.

For authentication you can use next-auth ( it changed to Auth.js ) and for a custom authentication guide you may want to follow my post here : https://dev.to/ekimcem/nextauthjs-authjs-credential-authentication-with-methods-you-need--21al

At the next level of your journey, I suggest you to take a look at Node.JS ( and my favorite backend framework is Express.) The reason is try to understand how backend works instead of get familiar with a new language. ( Also Node.JS is very powerful.)

And as @Sussex Spaniel said, Prisma is an ORM that you can manipulate (CRUD) your database.

I hope it helps @Northeast Congo Lion !

oh so you recommend me use another thing as backend for example express or nestjs. But in that case then i should have auth in backend side right? without using nextauth

Actually thats not the first stap, In the api folder of Next project, you can create a backend, but after a while you may need a larger backend then you may continue with the frameworks that you mentioned.

And, you are right and wrong 😅 , You can also connect next-auth to your custom authentication backend, but you can also check the password maching in nextauth too ( becuase it is also works on server side not client side) it is up to you

i know im like running first i need to be slower but not use, they are so many tutorial and diff way to do things. i will need a big api i think? let my tell you main functions of my software: generate invoice, list user, create user, create admin user, have roles acl, manage inventory (products), manage isp routers using another api

got already my frontend using nextjs13 just need to figure which backend solution is best for my use case

and why expressjs instead of nestjs?

well actually, if a response returns in under 10 seconds, next api will be enough. But if you do some long-term jobs in backend ( like scraping) you should have another microservcie.

Well, i do not have an exact answer to this, express seems more useful to me thats the only case 😄

got it, thank you so much for the tips both @Polar bear @ekimcem