Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring the Decision Data Store service

Updated on March 11, 2021

This content applies only to On-premises and Client-managed cloud environments

Store decision management data in a backing database, such as Cassandra, and manage the cluster by configuring the Decision Data Store (DDS) service. Examples of decision management data include customer data, decision results, and input data for adaptive and predictive models.

In on-premises and client-managed cloud environments, you have the following deployment options for Cassandra:

In this model, you need to install and operate your own Cassandra cluster, and connect it to Pega Platform. This option is recommended as it ensures future compatibility. For more information, see Connecting to an external Cassandra database.
Managed (embedded, internal)

In this model, the nodes that are designated to hosting the Decision Data Store have their Cassandra Java virtual machine (JVM) started and stopped for them, by the JVM that is hosting the Pega Platform instance. This type of configuration is deprecated starting in Pega Platform version 8.6 and therefore does not ensure future compatibility. It is not recommended for new deployments. For more information, see:

In Pega Cloud environments, the Cassandra database is preconfigured. No action is required.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us