In short, Configuration vs Features, in Drupal 7, fight!

As always, technical advantages, or other hard facts, as we don't do discussions here. Drupal 7 specific to limit to scope, as CMI vs Features is a completely different discussion.

  • No contest - Configuration wins! But I have no facts to back that up, other than the fact I've been using it for a few months now and wouldn't even dream of going back to features. It's leaner, meaner, more easily extendable and generally a pleasure to work with
    – Clive
    Commented Nov 29, 2012 at 13:03
  • @Clive Which version are you using? I've only looked at the project page, but is 1.x purely a 'featureless' Features, with 2.x being more D8-ish?
    – Chapabu
    Commented Nov 29, 2012 at 15:05
  • @Chapabu, yes, I believe those two statements are correct. After a quick glance at 2.x, I'm having difficulties understanding how Config differs from "One really big monolithic feature"-Feature, hence my question. :)
    – Letharion
    Commented Nov 29, 2012 at 15:29
  • 1
    I just read a technical fact right there! :) DI is a good thing, but it's not obvious to me how it plays a part here. Can you elaborate on that? :)
    – Letharion
    Commented Nov 29, 2012 at 15:38
  • 2
    @Letharion Thing is the DI/PSR-0 stuff isn't really a method for comparison between Config/Features, it's just how the codebase is laid out (i.e. 'namespaced' paths like lib/Drupal/node/Plugin/Core/Entity/Node.php for the node controller in D8). Don't get me wrong it's great that things are moving in this direction, but I wouldn't necessarily class that as an advantage over Features as such. I'm afraid I haven't got anything tangible to say about the difference really, except that I always found Features 'clunky' and I don't get that feeling using Config :)
    – Clive
    Commented Nov 29, 2012 at 16:19

1 Answer 1


Watch Configuration for the future, because it more closely follows the model of Drupal 8. But I wouldn't suggest using it for now, because it is in alpha state, which means you need to be prepared to hack on it to keep it working, and you need to constantly update it, because it will not get formal Security Advisories if security issues are discovered.

Features is at 1.0, so it's a more stable choice for projects going to production soon, as you can trust that minor version updates will not break your existing features.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.