Ultimate Guide To Drupal 8.6

Configuration Management System
One of the major improvements in Drupal 8, for both developers and site builders, is the new configuration management system. This allows sites that are
following the best practice of having a "development," "staging," and "production" environment to seamlessly move configuration from one environment to
another.
All configuration changes (both standard admin settings forms, such as site name, as well as any "configuration entity," such as views or content types), is
run through a standard configuration API. Each environment has a “sync” directory to hold configuration changes from other environments that are about
to be imported for review. For performance, active configuration is stored in a config table in the database, though the storage location is swappable (e.g.
to something like Redis or Cassandra) and when importing/exporting configuration, configuration is stored in YAML files.
Drupal 8 also ships with a basic UI to do both single and full configuration imports and exports, and view differences between them prior to importing
changes.
Configuration can also be moved around via the command line
with tools such as Drush, which is handy when keeping your
configuration in version control systems such as Git.
There are also a variety of contributed projects which build on top
of the configuration management system, such as the
configuration split module, which provides the ability to keep
different sets of configuration on one environment vs. another.
Future versions of Drupal 8 plan to include more of this
functionality as part of core.
And what about content deployment? The goal is for the new
workspaces module to handle that use case! See the workflows
chapter for more information.
36