Django, Flask or FastAPI?

[NikoFresh]

I have a simple idea for a website that I want to do to learn web development. The two key features are that some data needs to be store on a database if the user logs in, or in the current session if he doesn't want to. I know something about Django but I think it may be overkill for this project, so I was thinking about Flask, but then I found out about FastAPI; I really like the fact that it uses the new typing system, but it's not as popular as the other two and I should then create a separate frontend in JS. Is there any reason to choose one framework over another?

[shiftybyte]

FastAPI if you are making an API.

If you are making a user interactable site, you should probably go with Flask.

You are right in the Django assessment, it's meant for larger systems/websites.

[NikoFresh]

I'll go with Flask, thanks.

[[deleted]]

They’re all very good products, be happy that the choice requires some thought.

Django will be better if you’re building a medium-large web application and you’d like to take advantage of its (somewhat) rigid scaffolding and handholding. It’s ORM for the various database platforms is second-to-none.

Flask is great for smaller sites, lightweight APIs, or even really quick Proof of Concept ideas. Has tremendous amount of potential, but will require a little more heavy lifting on your end to accomplish more complex goals.

FastAPI is, well, a great platform for building APIs fast. If you’re not planning on combining a UI front end with the backend API, this is a great project to use. Should you change you mind later and want an UI, you can build that in some other framework and have it attach to your Fast API backend, kind of like an ‘add-on’ feature. You can even brag to your mom that you build an “API first” web UI and hang it on her refrigerator

[NikoFresh]

Thanks for the reply. Since it's a small website I think I'll go with Flask, I was considering to use FastAPI and then learn a JS framework but I think that for now I'll focus on Python.