---
title: Sitecore 9.3 Scalability
description: The release of Sitecore 9.3 introduces a number of improvements to Sitecore's architecture, including numerous updated components and databases.
publish date: 2020-05-05
author: Prasanth Nittala
image: https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/blog_hero_sc93-scalability.jpg?rev=bd326e8199e642ebbef3e60dba0db3c3
url: http://www-qa.oshyn.com/blog/2020/05/sitecore-9-3-scalability
---
# Sitecore 9.3 Scalability

![Scalable](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/blog_hero_sc93-scalability.jpg?rev=bd326e8199e642ebbef3e60dba0db3c3&hash=00F5D590D5AE24E1D07957453544F545)

The initial release of Sitecore 9.3 has brought a number of improvements to its architecture. With Sitecore 9.3, there are numerous components and databases — and it’s really helpful to see the communication flows / scalability of the components. Before viewing the diagram, it is good to understand the different Sitecore roles, xConnect application roles, and databases that are involved:

Sitecore roles:

- Content Delivery
- Content Management (with EXM Dispatch)
- Processing
- Reporting roles

xConnect application roles:

- Collection API
- Collection Search API
- Marketing Operations API
- Marketing Reporting API
- Reference Data API
- Search Indexer Job
- Marketing Engine Job
- Sitecore Cortex Processing Engine
- Sitecore Cortex Blob Storage service
- Sitecore Cortex Table Storage serviceSitecore Cortex Reporting service
- Universal Tracker Collection service
- Universal Tracker Processing server

Additional Components:

- Sitecore Identity Server (SIS).

Databases:

- Core
- Master
- Web
- Experience Forms
- Reporting
- Processing.Pools
- Processing.Tasks
- ProcessingEngineStorage
- ProcessingEngineTasks
- Universal Tracking database
- ReferenceData
- Messaging
- Marketing Automation
- ShardMapManager
- Shard0
- Shard1

Additionally:

- Please note that the diagram shows which components can be scaled horizontally. It does not include the database scalability options — as I assumed it to be a “highly available” database whether it exists on a single server or multiple database servers.
- The Solr component can be replaced with Azure Search component as needed.
- We cannot set up multiple instances of SIS behind load balancer due to encrypted cookie that can only be decrypted by the instance of SIS that encrypted/issued that cookie.
- We can set up Content Publishing component on separate server to support publishing, which is not shown in this piece.


![Cortex Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/2.png?rev=58de210dc99541b49db25e50bab3e75c?)

1. Cortex Communication Flow

![XConnect Analytics Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/3.png?rev=df3b456369504282b68ada453b821531?)

2. XConnect Analytics Communication Flow

![Universal Tracker Collection Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/4.png?rev=1a52bcb536ca4de2bcd04264a1d6355c?)

3. Universal Tracker Collection Communication Flow

![XConnect Reference Data Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/5.png?rev=e41264a61ed74325ae369dd0d9498053?)

4. XConnect Reference Data Communication Flow

![XConnect Collection & Indexer Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/6.png?rev=ceb11cc589094ab8bd9c1ce4e41169c0?)

5. XConnect Collection & Indexer Communication Flow

![XP Processing Server Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/7.png?rev=d1a7a672bf7444979ec86b8de68b69fc?)

6. XP Processing Server Communication Flow

![XP Reporting Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/8.png?rev=9b7aaa8be0b34681a0e1b2feed8d3665?)

7. XP Reporting Communication Flow

![XP CM Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/9.png?rev=b905a93cb9614c0f94e111865dfb8164?)

8. XP CM Communication Flow

![XP CD Communication Flow](https://www-qa.oshyn.com/-/media/Oshyn/Insights/Blog/20200505-Sitecore-9_3-Scalability/10.png?rev=8e076990aa6044d9a0ef679c751457ef?)

9. XP CD Communication Flow


As you can see in the diagram, you can have the following:

- Multiple Content Delivery servers
- Multiple Content Management servers
- Multiple Processing servers
- Multiple Reporting servers
- Multiple Solr servers
- Multiple xConnect Search API servers
- Multiple xConnect Collection API servers
- Multiple xConnect Reference Data service API servers
- Multiple xConnect Marketing Automation Reporting API servers
- Multiple xConnect Marketing Automation Operations API servers
- Multiple xConnect Marketing Engine Jobs
- Multiple xConnect Universal Tracker Processing service servers
- Multiple xConnect Universal Tracker Collection service servers
- Multiple xConnect Sitecore Cortex Reporting service
- Multiple xConnect Sitecore Cortex Table Storage service
- Multiple xConnect Sitecore Cortex Blob Storage service
- Multiple xConnect Sitecore Cortex Processing Engine

You can scale each of these components individually to suit your application needs. This provides a highly scalable Sitecore 9.3 architecture. I hope you find it helpful, and feel free to comment and let me know if there is anything misrepresented in here.