Using Features to manage configuration
Migrating or synchronizing databases between environments:
Manually updating configuration between environments:-
Writing custom code for all configuration changes:
Drupal components that can be managed with Features
Features supported components
1.Content types: Selecting a content type as a component of a feature will automatically include all the fields associated with that content type and Taxonomy vocabularies referenced by any Term reference field (although in the case of a Term reference field, Features will not include the vocabulary terms).
2.Fields: Although individual fields may be selected as a component of a feature, fields are automatically added as dependencies when creating features with content type components, and are not typically added manually.
3.Image styles: Custom image styles are available as components to be exported as features.
4.Text formats: There is typically not as much configuration involved with text input filters as there is for content types or Views, but it is definitely easier to add any custom text format filter configuration to an easily-managed Features generated module, than it is to remember what text format filter changes you made in your development site that need to be manually configured when you are ready to launch the live version of your site
5.Menus: On large sites, menu entries can become quite extensive and tedious to manage manually.
6.Taxonomies: Although useful for exporting custom vocabularies that are associated to Term reference fields of an exported content type, the taxonomy Features component does not include the terms associated with the exported vocabularies
7.Views: Custom Views are an excellent candidate for a Features module.
8.Roles and permissions: The ability to manage the configuration of roles and permissions on a simple site may not be all that useful. However, once you start modifying a number of permissions and adding more than a couple custom roles to your site, you will quickly come to appreciate the ability to manage this type of configuration with a Features-generated module.
Drupal components supported with additional modules
1.Core Blocks: The Features module by itself does not support core blocks
2.Content: Typically, you wouldn’t want to manage content between environments or different sites with Features. However, there are some cases where there is core content for a site that will be exactly the same between environments.
3.Vocabulary terms: Many times, you will have a vocabulary with terms that are not meant to be manipulated by anyone, but administrative users. Or, you may have a custom view that uses a particular vocabulary term as the value for a term-based filter. These types of vocabularies are excellent candidates for managing as Features-generated modules. This extended Features functionality is provided by the UUID Features Integration module.
4.Variables: Any variables that are in the Drupal variables table can be added as a component to a Features-generated module by installing the Strongarm module (http://drupal.org/project/strongarm).