What is Django REST framework?
Who uses Django REST framework?
Django REST framework Integrations
Here are some stack decisions, common use cases and reviews by companies and developers who chose Django REST framework in their tech stack.
Python's GraphQL version – Graphene – has some critical disadvantages, that we found critical:
- Lack of code optimisation. It is also hard to write optimized code because of graphene node API.
- Nonsecure by default. By using reversed fks, you can get a lot of extra data. To stop this, we have to explicit exclude wrong fields, which seems to be error prone.
- Nonflexible code structure. You can't make abstract
graphene.ObjectType class, this limits us a lot.
These are some reasons, that make us move to Django REST framework .
I’ve been using Django for the last year on and off to do my backend API. I’m getting a bit frustrated with the Django REST framework with the setup of the serializers and Django for the lack of web sockets. I’m considering either Spring or .NET Core. I’m familiar with Kotlin and C# but I’ve not built any substantial projects with them. I like OOP, building a desktop app, web API, and also the potential to get a job in the future or building a tool at work to manage my documents, dashboard and processes point cloud data.
I’m familiar with c/cpp, TypeScript.
I would love your insights on where I should go.
Django REST framework's Features
- The Web browsable API is a huge usability win for your developers.
- Authentication policies including OAuth1a and OAuth2 out of the box.
- Serialization that supports both ORM and non-ORM data sources.
- Customizable all the way down - just use regular function-based views if you don't need the more powerful features.
- Extensive documentation, and great community support.
- Used and trusted by large companies such as Mozilla and Eventbrite.