A state of REST.
summary
Compares three Django API libraries with concrete differences: TastyPie is a monolithic resource (≈2,100 GitHub watchers) that's easy to drop in but becomes cumbersome and slow; Django REST Framework uses stand-alone serializer classes, viewsets and routers, and includes OAuth2 support and browserable API; django-nap is lightweight, supports JSON, MessagePack and one format at a time, uses a publisher routing model, and replaced TastyPie in a production Kogan rollout; rate limiting is split into a separate django-rated package.
AI-written summary · about
chapters (14)
- 0:00Intro
- 3:09Comparing APIs
- 5:46Authentication
- 6:47NAP
- 7:04Authorization
- 7:31Django REST
- 9:26Tasty Pie
- 11:32Shape
- 12:14Pagination
- 13:52Rate Limiting
- 15:05Filtering
- 16:36API Versioning
- 18:08Generic Views
- 21:44Publisher Models
related talks
25mThe evolution of a RESTful Django backend
46mIntroducing Django REST framework
26mDjango, REST and OpenAPI - a gentle introduction
26mWhat it's really like building RESTful APIs with Django
27mBuilding a REST API with Django & Django REST Framework
25mWrite an API for Almost Anything (or The Amazing Power and Flexibility of Django Rest Framework)
21mBuilding Powerful APIs with Django, Django Rest Framework, and OpenAPI
33mNo Holds Barred Web Framework Battle