Although Preston mentions at the outset that there are trade-offs that come with decoupling, he addresses these two posts to developers who have determined that decoupling Drupal entirely is the appropriate course of action for their needs.

In this case, Preston recommends Ember as a prime candidate to underpin Drupal-backed JavaScript applications, primarily due to its reach, its coverage, and its ease of use. It also has an open-source ethos and a welcoming community. His two-part series is intended to help readers attain escape velocity quickly, by exploring the inner workings of Ember, foundational concepts of Ember's ecosystem, how to decouple Drupal with an Ember front end, and what the future could bring in terms of more Ember within Drupal. By the end of the series he's assembled a simple Drupal content browser powered by Ember.