To determine the right kind of framework for your project is a very complicated task. As the potential of your project is directly related to the type of framework you choose. You have to consider many things while choosing the right framework for you.

comparison of the angular amber backbone js

Selecting your Javascript Framework:

AngularJS, BackboneJS and EmberJS are alike in many ways such as they are used to create single web page applications using the MV* design pattern, are open sourced and are released under the MIT license.  Today, the internet is evolving, old technologies get obliterated swiftly and new technologies commence rapidly. Keeping this in mind let’s discuss these three frameworks in detail.

AngularJS: It was originally developed by Misko Hevery and Adam Abrons in the year 2009 and its latest version is 1.4.3. AngularJS is a structured framework for dynamic webpages and is designed for developers as well as designers. It lets you extend HTML, CSS and JavaScript and helps the developer to improve the client side applications. Its core features are two-way data binding, templates, MVC, dependency injection, directives, expressions, modules, scope and filters.

BackboneJS: It was developed by Jeremy Ashkenas. It is used for single web page applications and also to integrate different parts of the web applications. It’s light weight javascript library. It allows you to develop client-side applications or mobile applications by Javascript functions. And as the name suggest it acts as a backbone for your project (basically organizes the code).

EmberJS:  It was developed by Yehuda Katz and released in December 2011. It uses MVC architecture and is used to develop web applications for client side framework.  In this framework, the route is used as a model, handlebar template as view and controller as the model.

Basics – Model View Controller:

Model: It handles data and business logic

View: It presents data to the users through layout and format

Controller: It receives user requests and calls back to the model to choose a proper view

It provides a clear division between the application logic and User Interface (presentation).

It enables simplicity and maintainability easily.

Common Features:

Routing: It maps your URLs to a function.

Data Binding: It allows alterations in the model data to be updates or modifications in the view to be automatically updated in the model.

On the basis of the model, it automatically generates everything past the hash tag.

Each has active communities:

  1. GitHub Stars:

Angular: 36,270

Backbone: 21,032

Ember: 13,044

  1. StackOverflow Questions:

Angular: 75,000

Backbone: 24,347

Ember: 17,708

  1. GitHub Contributors:

Angular: 1,205

Backbone: 252

Ember: 464

  1. Third-Party Modules:

Angular: 1,279

Backbone: 257

Ember: 725

  1. YouTube Videos:

Angular: 102,000

Backbone: 12,500

Ember: 9,690

  1. Chrome Extension Users:

Angular: 266,719

Backbone: 13,452

Ember: 63,614

Over the last few years angular has garnered more interest and based on that below are relative interest in terms on Google:


Angular: 0

Backbone: 1

Ember: 0


Angular: 0

Backbone: 4

Ember: 0


Angular: 7

Backbone: 6

Ember: 2


Angular: 55

Backbone: 5

Ember: 2


Angular: 90

Backbone: 2

Ember: 1

Top 5 Nationalities Searches:


  1. India
  2. Israel
  3. Belarus
  4. Bangladesh
  5. United Kingdom


  1. India
  2. South Korea
  3. United States
  4. Ukraine
  5. Canada


  1. India
  2. US
  3. Canada
  4. Germany
  5. UK

So how are you going to decide?

You don’t want to lose your user just because your web page takes more time to load (framework size matters).

  1. Backbone: 506kb, Extension: underscore.js: 4kb, Total: 9.6kb
  2. Ember: 40kb
  3. Angular: 46kb

Below are some pros and cons of all the three frameworks:

  • Angular:


  1. Two-way binding allows automatic integration of data between model & view components.
  2. Is promoted by Google, leading to new innovations and tools.
  3. Largest community leading to answers and new development
  4. It is written for testability with modularized code that leads to clarity and strong built-in services.


  1. It has intricate directives API.
  2. The prototypical inheritance of scope hierarchy is new for developers coming from object-oriented languages.
  3. In the view layer, it can’t be tested in exclusion and it may lead to jumbled code.
  4. Pages will often run when a directive name is spelled incorrectly or function scope is undefined.
  • Backbone:


  1. Fast and lightweight
  2. Linear learning code
  3. Flexible


  1. No two-way data binding increases boilerplate.
  2. Many choices for 3rd party frameworks must be made.
  3. Be careful when you make changes as the views manipulate the DOM directly or your CSS might fail.
  • Ember:


  1. Strong data layer that integrates with RoR or other JSON APIs.
  2. Self-configures many aspects if you don’t define them yourself.
  3. Application loads and runs fast.


  1. Quick changes to the code can lead to outdated examples online.
  2. Tons of tags hurt readability and breaks CSS styling.