Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'd love to hear about your experiences with building APIs for single-page-apps between Rails and Django. Were you using rails-api or just straight-up Rails? Is there an equivalent API-focused "flavor" of Django, or if not, to what extent did you find it easy to choose not to use server-rendering functionality? I've used Django for more standard apps, and Rails for both, but I'm curious about the pros and cons of using Django for this sort of thing, because I have no experience with it.


Django REST Framework is the the most popular way to build APIs with Django. Lot of neat features out of the box such as throttling and permissions make it easy to build API endpoints.

http://www.django-rest-framework.org/


I'm still new to building APIs with Django. Last time I was immersed in Django, I was focused on server-side rendering.

I forgot to mention, part of the reason I went to Rails is its built-in support for building JSON APIs (at the time there was no clear winner among the Django API frameworks).

But now Django Rest Framework has matured quite well. By deriving everything from the model layer, it can help keep your API code nice and DRY.


> Is there an equivalent API-focused "flavor" of Django?

http://www.django-rest-framework.org/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: