I have worked with DRF in the past. It is a very nice framework. However, I came to believe that it is too low-level for new projects. Do you really want to handle at least the following pieces of boilerplate for every API or endpoint?<p>- Request parsing<p>- Content negotiation<p>- Creating&#x2F;rendering responses<p>- Subclassing or decorating custom views and&#x2F;or viewsets<p>- Model mixins, CRUD glue<p>- Routing<p>- Content-type parsing and rendering<p>- Serialization&#x2F;deserialization<p>- Validation<p>- Authentication<p>- Filtering<p>- Pagination<p>Personally, I found it was harder to get from zero to anything when having to slog through that level of verbosity. I&#x27;d rather save brain cycles for harder problems.<p>It was this experience on the job that led to the design of a better approach with Ramses: <a href="http:&#x2F;&#x2F;ramses.tech" rel="nofollow">http:&#x2F;&#x2F;ramses.tech</a>. You can also generate docs, tests and client libraries this way. If you like the look of that, I will make you an end-to-end prototype for free to help drive home the concept.<p>Some other awesome projects along the same lines are <a href="http:&#x2F;&#x2F;postgrest.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;postgrest.com&#x2F;</a> and <a href="https:&#x2F;&#x2F;flask-restless.readthedocs.org&#x2F;en&#x2F;stable&#x2F;" rel="nofollow">https:&#x2F;&#x2F;flask-restless.readthedocs.org&#x2F;en&#x2F;stable&#x2F;</a>