So here's our first installment of a blog series that will point to some of the best thinking on decoupled in general, and decoupled Drupal in particular.
We're starting with a short blog series by Preston So, Development Manager, Acquia Labs: Decoupled Drupal and Ember.
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.
You can access both posts here: Decoupled Drupal and Ember.
Or check 'em out one at a time:
Also, on the decoupled tip: Check out the brand new ebook from Acquia: API-First Drupal: On the Road to Publish Once, Access Everywhere. It's a solid intro, with four different case studies illustrating different use cases. A great overview, and a valuable asset to circulate to non-technical colleagues.