QuestionQ29

Data Architecture

A multinational travel agency has recently adopted Adobe Experience Platform as its primary tool for managing customer data. Its current system uses a traditional Relational Database Management System (RDBMS), with customer data stored in several tables: one for profiles containing unique customer IDs, emails, and names, and another for transactions recording each customer's bookings and trip details. The agency intends to migrate this data to Adobe Real-Time CDP while preserving the same accessibility and relational character in its new data model.

What is the most efficient strategy for translating the travel agency's RDBMS data model to Adobe Real-Time CDP's NoSQL Experience Data Model (XDM) while maintaining customer-booking relationships?

Explanation

Adobe XDM can model related entities in separate schemas. A relationship field in the source schema points to the primary identity of the referenced schema, so using the unique customer ID to link customer-profile and transaction schemas preserves the customer-to-booking relationship while keeping each entity independently modeled.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!