Last weekend I gave a talk on "Footless Drupal" about how Drupal 8 is using declarative programming for configuration, how the Config in Code (CINC) module is aiming to backport that to Drupal 7, and how it's already possible to use custom configuration workflows outside the default Drupal interfaces.
Recently we had the task of loading data from a content type with 350 fields. The overhead of the Views module caused PHP timeouts when exporting all the nodes. Loading an entire node means JOINing the node table by entity_id with each related field table, and at 350 fields the query runs slow.
During a recent Drupal 8 project we needed to collect structured address information outside the context of an entity. Specifically, adding a section for address and phone number to the Basic Site Settings configuration page. As it turns out, the same functionality you get on entities is now also available to the Form API.
Here are a few specific factors that make decoupled Drupal a good approach for a project – as well as a few that don’t.