Backbone Framework benefits

  

Backbone's main benefits, regardless of your target platform or device, include helping:

• Organize the structure to your application
• Simplify server-side persistence
• Decouple the DOM from your page's data
• Model data, views and routers in a succinct manner
• Provide DOM, model and collection synchronization

  Benefits of Backbone Frameworks are:

•     Core components: Model, View, Collection, Router. Enforces its own flavor of MV*
•     Good documentation, with more improvements on the way
•     Used by large companies such as SoundCloud and Foursquare to build non-trivial applications
•     Event-driven communication between views and models. As we'll see, it's relatively straight-forward to add event listeners to any attribute in a model, giving developers fine-grained control over what changes in the view
•     Supports data bindings through manual events or a separate Key-value observing (KVO) library
•     Great support for RESTful interfaces out of the box, so models can be easily tied to a backend
•     Extensive eventing system. It's trivial to add support for pub/sub in Backbone
•     Prototypes are instantiated with the new keyword, which some developers prefer
•     Agnostic about templating frameworks, however Underscore's micro-templating is available by default. Backbone works well with libraries like Handlebars
•     Doesn't support deeply nested models, though there are Backbone plugins such as this which can help
•     Clear and flexible conventions for structuring applications. Backbone doesn't force usage of all of its components and can work with only those needed.