Skip to main content

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

Deployment options for storing customer data

Updated on August 27, 2020

When implementing Pega Customer Decision Hub for Financial Services, you can improve performance or reduce deployment effort by choosing either a Decision Data Store (DDS) implementation or a combined relational and DDS implementation for your customer analytical data store.

Relational implementation

In a relational-only databases solution, your customer analytic data store has the highest level of compatibility with Pega Platform functionalities. Relational implementation is the most tested and proven solution.

Note: With this implementation, your performance is slower than with the DDS implementation and requires you to work with your database administrators to index and optimize your relational tables.

Select this deployment option for simulation testing, as it relies on data segmentation.

For more information, see Simulation testing.

Combined relational and DDS implementation

With the combined relational and DDS databases, you can reduce implementation effort and maximize reuse, particularly if you deploy applications that need to support audience-driven marketing campaigns, or multi-level decisioning.

In this solution, your customer analytic data store is contained in both SQL and NoSQL data stores and are replicated and maintained within Pega Platform for maximum flexibility. For more information, see Loading your data to the customer analytics data store.

Decision Data Store implementation

In a DDS-only solution, your customer analytic data store is contained in Pega Platform by using NoSQL technology, which allows for handling large volumes of data and, as a result, helps to avoid performance issues.

Select this deployment option when:

  • You have performance requirements of near real-time responses or a database that exceeds over a hundred million of customer records.
  • You want to deploy your application using only the inbound Pega Customer Decision Hub (a centralized component that handles business needs) or in analytics-driven decision processes.
    Note: Do not use the DDS implementation for outbound marketing.

The DDS does not support:

Segmentation rules
A Pega Customer Decision Hub feature with which you can create a static list of customers to use in traditional outbound campaigns.
Exclusion lists
Lists that specify entities that do not receive actions and offers.
  • Previous topic Understanding how Pega integrates with your systems
  • Next topic Data objects in Pega Customer Decision Hub for Financial Services

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