FastAPI Router || FastAPI structure bigger application

In this part, I answered the following question:

1.What is router?
3.How to use FastAPI router?

Feel free to leave comment about my content.

you can find file of this part from my github repository:

[kishanchauhan]

I think it's well structured, I am about to start a big project in FastAPI and I'm glad I ran to your videos, I am going to check out your FastAPI video series hope they will be helpful as well, As a Django developer, I found this project structure video very easy and helpful. Thank you very much

[AliSattarBarani]

Thanks i was able to solve my issue through your video. It solved by just adding the line below:


Also I'm wondering why you're creating the same filename twice in a two different folders.
My suggestion is why you're not trying to create a single folder for each one of models, routes, schemas, dependencies and then you can create a files according to your needs, I mean something like this below:

models:
--- user.py
--- post.py

routes:
--- user.py
--- post.py

and so on

[jaideepadhvaryu]

Very nicely done structure. May be you should longer video with more step-by-step. But this too is very helpful. You should also match client side, say react based structure.

[raymondmichael]

Can you create the same structure using mongodb instead of sql, or i really love how you structured the project

[gloxon]

The link to your repo does not contain the initial code, rather it contains just the final code. That makes it difficult for a beginner to pick up.

[JC.]

is this structure better than the recommended method from the fastapi author?

[curioussekhar]

can we have a nosql mongodb structure please?