Question

I have read a couple of articles about using new JS frameworks like Backbone.js or Ember.js

I have come up to this statement:
If I use a JS framework like Backbone.js/Ember.js, I then move the logic from the back-end (Django) to the front-end.

Therefore, will Django actually be used only for its Models?
Does that mean that Django Views and Django Template are not needed anymore and the Django back-end is kinda turn into a “basic” REST API that will be consumed by the front end.

Do you agree? Is it then the purpose of Django in this case?

Is turning the django backend into a REST API one of the most suitable use case when using a framework like Backbone.js/Ember.js for the front-end?

Thanks.

Answer 1

Django is perfectly fine to be used this way, you still get the admin, the models, the orm and all the third-party plugins. However, it isn’t blazingly fast, so if you’re doing simple document level, non-relational REST mapping, you might wan’t to look into node.js and mongoDB for instance.

If you’re sticking with django (like we are, we like the structure it gives us), you can use one of the REST plugins:

• Django Rest Framework A perfect match since DRF 2.0, under very active development!
• Django Tastypie (checkout backbone-tastypie.js for integration)
• Django Piston (might be a bit stale or has development picked up lately?)

If you only want to work with frontend development, checkout the Backend-as-a-Service places like cloudmine.me or firebase.com that handle all backend stuff for you, for a price of course.