This is very good! It's the most comprehensive guide of how to organize a large FastAPI project I've seen. Which is important, because FastAPI is unopinonated,

This is very good! It's the most comprehensive guide of how to organize a large FastAPI project I've seen. Which is important, because FastAPI is unopinonated, so there's onboarding cost to getting a team on the same page-- strong opinions help alleviate that! It's more Rails-like then Django/Flask-like. Meaning, top-level organization by "M"/"V"/"C" as opposed to by "Blueprint." I mean, "models/blog.py" as opposed to "blog/models.py". Netflix Dispatch is an example project that organizes in the more Flask-Blueprint-like way (https://github.com/Netflix/dispatch/tree/master/src/dispatch https://github.com/Netflix/dispatch/tree/master/src/dispatch). I'm going to pour over this a bit longer, but that will take some time! So I wanted to leave some initial thoughts to people discovering this.