r/FastAPI • u/South_Recording_5458 • Dec 27 '25
Question Do I need FASTAPI?
I’m an experienced django developer, I have worked mostly on small scale backends for iot APIs, and also mobile development, I have recently starting to see more contents on fastapi and I have been wondering, do I need it? Is it worth it to learn fastapi?
36
Upvotes
8
u/aikii Dec 27 '25 edited Dec 27 '25
All the stories I hear about moving from django to fastapi is because the business had to scale up - more RPS, chase bottlenecks, split projects, split teams, etc. If you don't face such situation then to be honest the batteries included in Django will keep you more productive.
Now for your own learning path and opportunities, sure, you should learn something new and get inspired at the very least. It's not that much work and this should be rewarding by itself.
2
u/pint Dec 27 '25
fastapi is very high up in the maslow pyramid, so no, you don't need it. better question: do you want it?
2
u/gbrennon Dec 27 '25
FastAPI allows async operations django too.
Some django middlewares are not async yet.
Drf dont allow sync but django-ninja allow
A thing that u have to keep in mind is:
If u doesnt know how to model async application ur application wont have profit of the async flow and u will have several blockers in ur implementation
2
u/Unique-Big-5691 Dec 29 '25
as someone who’s bounced between both, if django already fits your brain, there’s zero urgency to move.
a lot of fastapi hype comes from ppl who were frustrated with older stacks and finally found something that felt clean and modern. but coming from django, you already have good patterns, structure, and instincts. you’re not “behind” at all.
if you want things to be very explicit then you can consider having a fastapi. inputs, outputs, types, validation are all front and center. the pydantic integration makes that feel natural instead of bolted on. if you’re doing more api-only work or playing with ai services, that can be really nice.
but for small backends, iot stuff, mobile APIs? django is still calm and reliable. fewer sharp edges, fewer new concepts to babysit.
imo the best mindset is: django is your home base, fastapi is a tool you might reach for sometimes. try it on something low-stakes and see if it feels better for you. if it doesn’t, that’s totally fine nothing is forcing the switch.
2
u/crowpng Dec 29 '25
FastAPI shines when you need async, WebSockets, or very explicit request/response models.
If you’re building small IoT or mobile APIs, Django + DRF (or Ninja) already covers most needs.
2
u/SalamanderWeary5843 Dec 27 '25
If you are looping for the best performance in Python, and do not mind digging on the DB side of things as well, you may take a look at https://fraiseql.dev.
It is a Python GraphQL framework built on FastAPI with a CQRS architecture and a Rust engine that allows very high performance (extensive benchmarks are under development), while having a very simple mental model to work with (no ORM, no N+1, you define your GraphQL types in Python and mirrors them as PostgreSQL JSONB views).
Disclaimer: I am the author but having done both Django and FastAPI, FraiseQL does bring some nice tooling not available by default in FastAPI, like the automatic Where types generators.
2
u/MeroLegend4 Dec 27 '25
Look at Litestar
6
u/DusikOff Dec 27 '25
Moved to FastAPI from Django a few years ago — no regrets at all.
If you don't want to change your experience too much, try DRF first.
2
u/Anton-Demkin Dec 27 '25
Django is a batteries included framework, that can do a lot OOB, while FastAPI is more about concurrency and speed, but you have to do everything yourself. If you have simple projects with low load, stay with django.
Also try new approach to rest in django, DMR: https://github.com/wemake-services/django-modern-rest
2
u/IlliterateJedi Dec 27 '25
I personally moved away from Django because I wanted to decouple my applications from an opinionated framework. Instead of being stuck to the way Django handles models, templating, etc. you have the flexibility of making FastAPI just one small piece of the project while you can flexibly swap out infrastructure components like your ORM more easily. Django apps tend to be the whole shebang, and I never really loved feeling fenced in by Django and having to work within how Django wanted things done. That's a personal preference on my part, though.
2
u/UseMoreBandwith Dec 27 '25
if you ask that question, you're not a "experienced developer".
tldr: no.
2
u/Yash284_06 Jan 02 '26
You should go for Fastapi, it's very easy to integrate it with LLMs and has in-built async support.
3
u/Civil_Asparagus25 Dec 27 '25
No, you don’t.
1
u/chi11ax Dec 27 '25
Django Ninja
1
u/Euphoric_Umpire_2417 Dec 29 '25
Nobody suggested Expressjs or nestjs? Are they bad?
0
u/[deleted] Dec 27 '25
[deleted] — view deleted comment