Platform Administration and Architecture

Scale vertically

The Sitecore Experience Platform can be vertically scaled dedicating an instance to a specific role, such as Content Delivery or Processing. You can scale out further by dedicating multiple instances to a specific task. Your topology will depend on your scaling requirements.

The following examples demonstrate how to scale out incrementally from a standalone instance (XP Single) to a fully scaled instance (XP Scaled). Keep in mind that:

  • The examples show databases arranged in functional groups based on ownership and does not seek to impose a particular server architecture. It is up to you to decide how you configure and scale SQL. Refer to the database scaling page for more information about what to take into consideration.

  • The examples assume that Solr is being used for xConnect search and content search and does not seek to impose a particular server architecture. It is up to you to decide how you configure and scale Solr.

  • The Marketing Automation Engine Windows Service can be extracted to a dedicated server. In the following examples, it is logically grouped with the Marketing Automation Operations role.

  • The xConnect Search Indexer Windows Service can be extracted to a dedicated server. In the following examples, it is logically grouped with the xConnect Search role.

Combined instances

In the following scenario, all core roles are combined and all XP services are combined. This is a pre-built topology that is also known as XP Single.

no-scaling-simple1.png

Note

In a developer environment, both instances are hosted on a single machine alongside all instances of Solr and all databases.

Dedicated Content Delivery instance

In the following scenario, Content Delivery has been extracted to a dedicated instance:

dedicated-cd-simple1.png

Important

This combination is not recommended in Azure as the Content Management role cannot be scaled out as easily as the Processing and Reporting Service roles. It is recommended that you always have a dedicated service plan for the Content Management environment.

Dedicated Content Management instance

In the following scenario, Content Management and Content Delivery have been extracted to dedicated instances, leaving a third core Sitecore instance to perform the processing and reporting roles:

combined-reporting-processing-simple1.png
  • Configure a single instance that performs xConnect Collection, xConnect Search, Marketing Automation Reporting, Marketing Automation Operations, and Reference Data roles.

  • Configure a dedicated Content Delivery instance.

  • Configure a combined Reporting and Processing role.

  • Configure a dedicated Content Management instance.

    • The Reporting role is performed by a dedicated instance - Content Management does not need access to the reporting connection string.

When Reporting and Content Management are combined, the server has direct access to the reporting database. When Reporting and Content Management are performed by separate servers Content Management communicates with Reporting over HTTPS.

Dedicated Processing and Reporting instances

In the following scenario, Processing and Reporting have been extracted to dedicated instances:

dedicated-reporting-processing-simple1.png
  • Configure a single instance that performs the xConnect Collection, xConnect Search, Marketing Automation Reporting, Marketing Automation Operations, and Reference Data roles.

  • Configure a dedicated Content Delivery instance.

  • Configure a dedicated Processing instance.

  • Configure a dedicated Reporting instance.

  • Configure a dedicated Content Management instance.

    • The Reporting role is performed by a dedicated instance - Content Management does not need access to the reporting connection string.

xConnect: Combined Collection and Search instance

In the following scenario, xConnect Collection and xConnect Search have been extracted to a combined instance:

combined-collection-search-simple1.png
  • Configure a combined xConnect Collection and xConnect Search instance.

  • Configure a combined Marketing Automation Reporting, Marketing Automation Operations, and Reference Data instance.

  • Configure a dedicated Content Delivery instance.

  • Configure a dedicated Processing instance.

  • Configure a dedicated Reporting instance.

  • Configure a dedicated Content Management instance.

    • The Reporting role is performed by a dedicated instance - Content Management does not need access to the reporting connection string.

xConnect: Dedicated Collection and Search instances

In the following scenario, Collection and Search have been split into two separate instances:

dedicated-collection-search-simple1.png
  • Configure a dedicated xConnect Collection instance.

  • Configure a dedicated xConnect Search instance.

  • Configure a combined Marketing Automation Reporting, Marketing Automation Operations, and Reference Data instance.

  • Configure a dedicated Content Delivery instance.

  • Configure a dedicated Processing instance.

  • Configure a dedicated Reporting instance.

  • Configure a dedicated Content Management instance.

    • The Reporting role is performed by a dedicated instance - Content Management does not need access to the reporting connection string.

Important

When Collection and Search are separated, each client - Content Delivery, Content Management, Processing - must be configured to use separate Collection and Search endpoints.

xDB: Dedicated Reference Data and Automation instances

ref-data-separate-simple1.png
  • Configure a a dedicated xConnect Collection instance.

  • Configure a dedicated xConnect Search instance.

  • Configure a dedicated Reference Data Service instance.

  • Configure a combined Marketing Automation Reporting and Marketing Automation Operations instance.

  • Configure a dedicated Content Delivery instance.

  • Configure a dedicated Processing instance.

  • Configure a dedicated Reporting instance.

  • Configure a dedicated Content Management instance.

    • The Reporting role is performed by a dedicated instance - Content Management does not need access to the reporting connection string.

Important

When Collection and Search are separated, each client - Content Delivery, Content Management, Processing - must be configured to use separate Collection and Search endpoints.

Fully scaled

In the following scenario, Marketing Automation Reporting and Marketing Automation Operations have been extracted to dedicated servers. At this point, every core role and XP service role is performed by dedicated server. This is a pre-built topology and is also known as XP Scaled.

fully-scaled-simple1.png