Hi @cresg820, author of ember-django-adapter here. I’m a fan of client-side adapters primarily because I feel an API consumer should conform to the API server, not the other way around.
APIs generally provide documentation regarding their nature and ability, and then it is up to the consumer to use it to accomplish whatever task is desired. I often have multiple consumers for my API (website, mobile, etc.), and I don’t believe any one of them should dictate how my API works.
All that said, there are several things you can do when setting up your API using Django REST Framework that make it more Ember-friendly, but are not too invasive. Ember understands that there are several different API styles out there, and that’s why they explicitly make it possible to create adapters. This feature of Ember is encouraged and well documented.
However, if you do decide to try server-side adapters, you might also consider @gordon_c’s adapter: https://github.com/g-cassie/ember-drf