When implementing Pega Customer Decision Hub, 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.
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.
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.
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.