Description

The following table describes differences between various Sitecore XP environments for the Sitecore Managed Cloud service as well as related Azure components.

Customers are able to purchase such configurations under both Prod and NonProd SLA.

Note:

1. Tiers and topologies are subject to availability. Check Sitecore Managed Cloud Standard – compatibility tables for the currently supported Tiers for provisioning new Sitecore Managed Cloud Standard sets as well as for the Microsoft Azure data center compatibility information. The environment tiers are designed in accordance with the Sitecore XP ARM templates with additional changes and clarifications required to deliver Managed Cloud specific service level agreements. Sitecore may update the recommended sizes from time to time to ensure the most efficient performance level. For details about the specific topology and size applied in a contract, customers should contact their Sitecore sales representatives.
2. Using the Basic App Service plan is not recommended as it is designed for the test environment and has a number of limitations, such as, no possibility to use backups at all, no autoscaling your instances, storage capacity only 10Gb and no opportunity to use Traffic manager to load balancing and no using Staging slots for development.

Experience Management

Component / Performance Rating	xM1 Extra Small	xM2 Small	xM3 Medium	xM4 Large	xM5 Extra Large
Approximate visits per month range	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000 - 10,000,000
Page views per month	500,000	1,000,000	5,000,000	10,000,000	50,000,000
Content Management Server – Azure Web App	1 x B2	1 x B2	1 x B2	1 x B2	1 x B2
Content Delivery Server – Azure Web App	1 x B2	2 x B2	3 x B2	4 x S3	8 x S3
xDB Processing Service – Azure Web App	-	-	-	-	-
xDB Reporting Service – Azure Web App	-	-	-	-	-
Core DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Analytics DB – SQL Azure	-	-	-	-	-
MongoDB – mLab on Azure	-	-	-	-	-
Search – Azure Search [1][2]	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1xEnterprise (4 nodes)	1xEnterprise (4 nodes)
Session State – Redis Cache	1 x C1	1 x C1	1 x C1	1 x C1	1 x C1

 

Experience Platform

Component / Performance Rating	xP0 Single	xP1 Extra Small	xP2 Small	xP3 Medium	xP4 Large	xP5 Extra Large
Approximate visits per month range	-	0- 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000 - 10,000,000
Page views per month	-	500,000	1,000,000	5,000,000	10,000,000	50,000,000
Content Management Server – Azure Web App	1 x B2	1 x B2	1 x B2	1 x B2	1 x B2	1 x B2
Content Delivery Server – Azure Web App	-	1 x B2	2 x B2	3 x B2	4 x S3	8 x S3
xDB Processing Service – Azure Web App	-	1 x B1	1 x B1	1 x B1	1 x B2	1 x B2
xDB Reporting Service – Azure Web App	-	1 x B1	1 x B1	1 x B2	1 x B2	1 x B2
Core DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Analytics DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S2	1 x S2	1 x S2
MongoDB – mLab on Azure	40 GB	40 GB	60 GB	120 GB	480 GB	700 GB
Search – Azure Search [1][2]	1 x S1 (1 RS x 1 P)	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	4 x S1 (2 RS x 2 P)	6 x S1 (2 RS x 3 P)	6 x S1 (2 RS x 3 P)
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1 x Basic	1xEnterprise (4 nodes)	1xEnterprise (4 nodes)
Session State – Redis Cache	1 x C1	1 x C1	1 x C1	1 x C1	1 x C1	1 x C1

 

Experience Database

Component / Performance Rating	xDB1 Extra Small	xDB2 Small	xDB3 Medium	xDB4 Large	xDB5 Extra Large
Approximate visits per month range	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000 - 10,000,000
Page views per month	500,000	1,000,000	5,000,000	10,000,000	50,000,000
Content Management Server – Azure Web App	-	-	-	-	-
Content Delivery Server – Azure Web App	-	-	-	-	-
xDB Processing Service – Azure Web App	1 x B1	1 x B1	1 x B1	1 x B2	1 x B2
xDB Reporting Service – Azure Web App	1 x B1	1 x B1	1 x B2	1 x B2	1 x B2
Core DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web DB – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Analytics DB – SQL Azure	1 x S1	1 x S1	1 x S2	1 x S2	1 x S2
MongoDB – mLab on Azure	40 GB	60 GB	120 GB	480 GB	700 GB
Search – Azure Search [1][2]	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	4 x S1 (2 RS x 2 P)	6 x S1 (2 RS x 3 P)	6 x S1 (2 RS x 3 P)
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1xEnterprise (4 nodes)	1xEnterprise (4 nodes)
Session State – Redis Cache	-	-	-	-	-

Notes

• [1] Azure Search size refers to Search Unit (SU), which is the product of replica and partitions used by the Azure Search service (R X P = SU). At a minimum, every service starts with 1 SU (one replica multiplied by one partition). See search units and SU combinations for more information.
• [2] The size of Azure Search Units for Managed Cloud topologies are double the size of what is defined in the ARM template article. This is due to Microsoft SLA for Azure Search, which requires a minimum of two replicas to guarantee 99.9% availability.
  As a cost saving measure all customers are initially set up with only 1 partition and then new partitions will be added as required. However, from a budgeting point of view you should expect to increase to the number of partitions listed by the end of the first year.
  The Single sizing is not designed for production usage so it is only set up with 1 Replica Set by default because no SLA should be required.
• [3] The size of Solr instances on SearchStax:
  

  Tier	Specification	Production and Non-Production – Max Requests / Month*
  XS	32 GB storage	1 Million
  S	32 GB storage	2 Million
  M	50 GB storage	10 Million
  L	75 GB storage	20 Million
  XL	75 GB storage	100 Million
  2XL	128 GB storage	100 Million
  3XL	256 GB storage	100 Million

  *- Customers exceeding the monthly entitlement will accrue overages against your contract.