Reference architecture

Abstract

Overview of the Sitecore XC distributed production deployment reference architecture, which is applicable for on-premise deployments or on hosted virtual machines.

The following figure shows the Sitecore XC distributed production deployment reference architecture, applicable for an on-premises deployment or on hosted virtual machines.

The diagram shows the main Sitecore XP and Sitecore XC roles and some of the main connections between them. In the context of a Commerce deployment, Sitecore XP is the entire Sitecore platform including Experience Management, Experience Platform, xDB, and xConnect.

The diagram groups the services that are typically bundled together on the same physical resources. This distribution of physical resources is considered the minimum in a typical production deployment.

DevOps_Reference_Architecture_9_1.png

The reference architecture for the Sitecore XC solution comprises four broad logical partitions:

  • Authoring: comprises Sitecore XP core services for creating, managing and publishing content. In a Commerce context, this includes hosting the Storefront and Business Tools for internal access.

  • Delivery: comprises Sitecore XP core services for displaying web content to visitors, and executing in-session personalization rules. In a Commerce context, this includes hosting the Storefront for visitor access.

  • Commerce Services: comprises Sitecore XC Engine application, processing, and Commerce storage roles.

    Note

    Sitecore XC stores Commerce data in the Shared and the Global Commerce database.

  • Experience Database: comprises Sitecore XP services and storage roles that collect and store experience data.

Service role

Description

Content Management (CM)

A Sitecore XP internal-facing web server that hosts client applications used by internal content authors for creating, managing and previewing content.

In a Commerce production deployment context, the CM hosts:

  • an instance of the Storefront and the dependent SXA framework for internal users to access external shopper data and other internal information.

  • internal connectors including Commerce Connect Core, and Commerce Engine Connect (CE Connect), which enable the Commerce Engine to connect with Content Management and the Storefront.

The reporting service is also deployed on the CM, which displays analytics data to internal users.

Content Delivery (CD)

A Sitecore XP external-facing web server for displaying web content to visitors, and for executing in-session personalization rules.

In a Commerce production deployment context, the CD hosts:

  • instance(s) of the externally-facing Storefront.

  • the Connect Core and CE Connect internal connectors.

Content databases

Sitecore XP databases including:

  • Master: store unpublished content managed via the CM; these belong in the authoring network.

  • Web: store the latest version of published Sitecore content; as part of the delivery network it serves its data to the CD.

  • Core: store configuration information about Sitecore user interfaces and accounts; they serve both the CM and CD.

    Note

    Sitecore Content databases do not store Commerce data. Commerce data is stored in the Commerce databases.

Commerce Engine roles

Deployed instances of core Commerce application roles, each serving distinct logical roles:

  • Shops: serves external requests from externally-facing Storefront(s).

  • Authoring: serves internal requests from the Business Tools.

  • Minions: a worker role that performs asynchronous background processing.

  • DevOps: a maintenance role for internal DevOps users (not shown in diagram).

Commerce databases

Two logically separated storage databases including:

  • Shared Environments: stores the Commerce data used on the Storefront(s).

  • Global: stores the configuration data that govern how the Engine roles function.

Business Tools (BizFX)

Business tools interface used by internal users. They communicate directly with the Commerce engine services via a dedicated Commerce EntityView core API.

Identity Server

Sitecore’s federated authentication service provider, for authenticating to the Business Tools and Commerce Engine.

xConnect

Collects visitor contact and interaction data from the CD.

Collection databases

Sitecore XP databases that store visitor contact and interaction data, for example: contacts, devices, locations, actions, engagement automation states.

Processing

Processes the real-time customer interaction data from Collection databases; aggregates and stores them in the Analytics databases for internal reporting.

Analytics databases

Stores analytics data from the Processing server.

Search indexes

Allow internal users to perform searches (for example, catalog items, orders, and customers).