Scaling and configuring Core roles
Core roles are instances of the core Sitecore application with certain features enabled or disabled. In a developer environment, a single combined instance that performs all roles. In a fully scaled deployment, a dedicated instance performs each role. The Core roles group includes both Experience Platform (for example, xDB Processing) and Experience Manager (for example, Content Delivery) roles.
Core roles share the following in common:
-
The ability to define a server role or combination of roles with a single switch in the
web.configfile. -
The ability to enable or disable configuration depending on the role.
-
A shared framework for patching configuration.
-
A default license file location.
Options for scaling Core roles
Options for scaling Core roles include:
-
Dedicating a server or app service to a particular role. Production environments must have at least one dedicated Content Delivery instance.
-
Combining roles. For example, you might choose to combine Content Management and xDB Processing if neither of those roles are experiencing heavy load. Refer to individual Core role pages for information about which combinations are supported.
-
Dedicating a particular job to a particular instance. For example, in a cluster of five Content Delivery instances, you might dedicate one instance to handle session expiration.
-
Setting up multiple instances. For example, you might set up multiple Content Delivery servers behind a load balancer or set up multiple xDB Processing instances to process tasks from the Processing Pool database.