Geek asks and answers

Trunk and Django, finding the best client-side architecture

I worked with Django as a backend and used jQuery for the interface. Now with web pages there was such a dynamic javascript started to get more and more complex and I feel the need for a better, more organized structure there.

I started reading about Backone, and it just looks like a backend approach to the interface (since it is an MVC infrastructure). This will make my code more structured, but some functions seem to overlap (e.g. models, URLs, ...)

I also read about using trunk with tastypie and django to implement a RESTful environment here . This is very cool, as the application will also be ready for the development of the phone.

Now my question is: is this architecture good or bad? what are the pros and cons of it, and if there is an easier way to achieve DRY client code (perhaps after following some set of rules / best practices)

Any personal experience is more than welcome :)

+5
source share
1 answer

, . , , , , , , http://joshbohde.com/blog/backbonejs-and-django, ( ), Backbone Django .

Django + Backbone , , NodeJS + Backbone. , Django/Python - , Backbone , ( ), , ( REST ) , , .

+5

More articles:


All Articles