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?

- Request parsing

- Content negotiation

- Creating/rendering responses

- Subclassing or decorating custom views and/or viewsets

- Model mixins, CRUD glue

- Routing

- Content-type parsing and rendering

- Serialization/deserialization

- Validation

- Authentication

- Filtering

- Pagination

Personally, I found it was harder to get from zero to anything when having to slog through that level of verbosity. I'd rather save brain cycles for harder problems.

It was this experience on the job that led to the design of a better approach with Ramses: http://ramses.tech. 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.

Some other awesome projects along the same lines are http://postgrest.com/ and https://flask-restless.readthedocs.org/en/stable/