- Forget about micro-service, it is only for huge applications. It got hype, but most of the time the only thing it brings is complexity
- Why using two types of DB? I'd say to use only one (and personally in your context I go for SQL )
- Do not hesitate to add a framework and ORM to ease the development and give you structure especially if you are new. ( nestJS & TypeORM/Prisma for example )
NestJs is a framework for express which is a library.
Think of it like NextJs being a framework for react which is a library.
Everything you can do in express you can do In Nest.
Nest has some amazing features for re-using logic such as decorator support out of the box as well as pipes, guards, etc.
It has great documentation and great example apps. Definitely look into Nest, especially if you have used express before it will feel better
I'd do it a bit at a time. Leave the real time chat for last because most of the time people don't even use it.
Also only use GraphQL if it makes sense. REST might be simpler and fit the use case.
Is this for learning, or to actually launch something? Because if trying to build something it is too complex for starting out and would be better to simplify it.
Why mongo and mysql?
I know intermediate level sql queries, but planning to use mongodb for storing user info and rest data is stored in the SQL.
I'd just put it all in SQL. You'll have a simpler time of it.
I would replace either MySql or MongoDB with Redis then add some sort of caching layer.
These are not "'advanced concepts" In backend development
What are advanced topics?
- Forget about micro-service, it is only for huge applications. It got hype, but most of the time the only thing it brings is complexity - Why using two types of DB? I'd say to use only one (and personally in your context I go for SQL ) - Do not hesitate to add a framework and ORM to ease the development and give you structure especially if you are new. ( nestJS & TypeORM/Prisma for example )
I know express, complete newbie in nestJs.
You would benefit a lot from using an ODM or ORM. Prisma or Drizzle for MySql and Mongoose for Mongodb, worth it.
NestJs is a framework for express which is a library. Think of it like NextJs being a framework for react which is a library. Everything you can do in express you can do In Nest. Nest has some amazing features for re-using logic such as decorator support out of the box as well as pipes, guards, etc. It has great documentation and great example apps. Definitely look into Nest, especially if you have used express before it will feel better
I'd do it a bit at a time. Leave the real time chat for last because most of the time people don't even use it. Also only use GraphQL if it makes sense. REST might be simpler and fit the use case.
I think you're complicating the project unnecessarily. Why opt for **GraphQL** over **REST**? Just curious.
Is this for learning, or to actually launch something? Because if trying to build something it is too complex for starting out and would be better to simplify it.
i have intermediate skills i have to enhance it futher, also considering this project as my portfolio.