---
title: "Scaling and configuring XP service roles"
slug: "scaling-and-configuring-xp-service-roles"
abstract: "Overview of the characteristics of XP service roles and available options."
---
# Scaling and configuring XP service roles

XP service roles run on a shared code base and can be combined or separated to meet scaling demands. In a developer environment, a single combined instance hosts all services. In a fully scaled deployment, a dedicated instance performs each role.

XP service roles have the following characteristics in common:

- The ability to combine roles by enabling and disabling a specific set of configuration files.
- The ability to set up [configuration environments](https://doc.sitecore.com/xp/en/developers/92/platform-administration-and-architecture/xp-services-configuration-overview.html "XP services configuration overview") - for example, different configurations for production and QA.
- A shared framework for patching configuration.

Options for scaling XP services include:

- Dedicating a server or app service to a particular role - for example, you might want to host a dedicated xConnect Collection service if you collect a lot of analytics data.
- Combining roles - for example, you might choose to combine the Marketing Automation Operations and Marketing Automation Reporting services if that area of the platform is not under load.
- Setting up multiple instances - for example, you might set up multiple xConnect Collection services behind a load balancer.