Installation Types

The Content Store can be installed in a number of different ways to satisfy different needs. Common installation types include:

Single computer

Everything (database, application server, Content Store) is installed on a single computer. This is usually the case for demonstration and developer installations.

Multiple application servers, single database

The application server and Content Store is installed on multiple computers, but all share a single database server. This kind of installation is common in large development environments.

Single web server, single application server and Content Store, single database

This is a common production installation structure for small sites.

Multiple web servers, multiple application servers/Content Stores, database rack

This is a common production installation structure for large sites, and is easily scalable.

Other configurations are, of course, possible.

In large organizations the Content Store often needs to be installed in several different configurations in order to meet the requirements of different environments:

Development

In a development environment there are typically several updates of several files several times a day. Depending on the number of developers working on a system and the potential for conflicting changes, developers may either:

  • Share a single development installation, or

  • Each use a personal Content Store installation but share a single database.

Test

A test environment is a complete Content Store installation on which 'current stable versions' can be tested. Code updates in this environment are typically carried out at longer intervals and in 'batches' rather than on the file level. In some organizations, the test environment may be merged with the staging environment.

Staging

A staging environment should be as similar to the production environment as practically possible: it should have the same software, the same configuration, and if possible the same hardware, firewall and network setup. This is the last stage before actual production, and is intended to catch "works on the test server but not in production" problems.

Production

A production environment is heavily optimized for high workloads and security.