Platform Administration and Architecture

Scale databases

This topic describes the scaling opportunities for each database type within the Sitecore Experience Platform.

Experience Manager

The following section describes options for scaling the Experience Manager databases.

Web

A web database is likely to have a high read volume. Standard recommendations include:

  • Dedicate a server per web database

  • Content Delivery server(s) and web databases should be physically close or in the same sub-region in Azure if possible

  • Consider Content Delivery clustering - either using SQL replication or multiple publishing targets

Transactional SQL Replication

There is experimental support for Transactional SQL replication of the web database - see the following articles for more information:

Master

The load on the master database depends on the number of concurrent authors. Standard recommendations include:

  • Dedicated server for master database or shared with core

  • Content Management server(s) and master database should be physically close or in the same sub-region in Azure if possible

  • Content Management server(s) and master database should be physically close to the largest group of authors

Note

Replication of the master database is not supported - refer to the following article for information about supported SQL scaling features: https://kb.sitecore.net/articles/423602

Core

All core roles (Content Management, Content Delivery, Processing, Reporting) require access to a core database. Standard recommendations include:

Note

Replication of the core database is not officially supported - refer to the following article for information about supported SQL scaling features: https://kb.sitecore.net/articles/423602

Experience Platform

The following section describes options for scaling the Experience Platform databases.

xDB Collection

The xDB Collection database is likely to experience high read/write activity, and supports sharding. Experience data is sharded in the following way:

  • Contact and interaction data is sharded by contact ID.

  • The identifiers index is sharded by identifier.

  • Device profiles are sharded by device profile ID.

MongoDB is available as an xDB Collection provider in Sitecore 9.0 Update 2 and later. Refer to the Installation Guide PDF for information about configuring this provider.

MongoDB supports sharded cluster configuration.

Reporting

The Reporting database is likely to experience high write volume, as it is constantly being written to by the processing server(s). Standard recommendations include:

  • Dedicated server for analytics database

  • Processing server(s) and analytics database should be physically close or in the same sub-region in Azure if possible

  • Tune batch aggregation options