Conceived on May 11, 2020
FastAPI actually plays very well with Django
You know me, I’m a Django fan.
It’s my preferred way of developing web apps, mainly because of the absolutely vast ecosystem of apps and libraries it has, and the fact that it is really well-designed.
I love how modular it is, and how it lets you use any of the parts you like and forget about the ones you don’t want.
This is going to be emphasized rather spectacularly in this article, as I’m going to do things nobody should ever have to do.
My only issue with Django was that it never really had a good way of making APIs.
I hate DRF with somewhat of a passion, I always found its API way too complicated and verbose, and never managed to grok it.
Even the simplest things felt cumbersome, and the moment your API objects deviated from looking exactly like your DB models, you were in a world of hurt.
I generally prefer writing a simple class-based view for my APIs, but then I don’t get automatic docs and other niceties.
It’s no surprise, then, that when I found FastAPI I was really excited, I really liked its autogenerated docs, dependency injection system, and lack of magical “request” objects or big JSON blobs.
It looked very simple, well-architected and with sane defaults, and I seriously considered developing the API for my company’s next product on it, but was apprehensive about two things:
It lacked Django’s ecosystem, and it didn’t have an ORM as good and well-integrated as Django’s.
I would also miss Django’s admin interface a lot.
It would have been great if FastAPI was a Django library, but I guess the asynchronicity wouldn’t have been possible.
Still, there’s no reason for DRF not to have an API as nice as FastAPI’s, but there’s no helping that.
A fantastical notion caught hold of me: What if I could combine FastAPI’s view serving with Django’s ORM and apps?
Verily, I say unto thee, it would be rad.
And that’s exactly what I did.