Reference Data Service overview¶
In this topic:
The Reference Data Service is a stand-alone xDB service that allows definition data to be stored and used within the xDB environment. Examples of data that can be stored in the Reference Data Service include:
- Marketing Operations definitions, such as goals, outcomes, and and automation plans
- Browser agents
- Site names
- Airport codes
- Loyalty scheme tier names
The Reference Data Service can be used by features such as interaction aggregation to look up additional information about referenced entities by way of a key. For example, an interaction aggregation processor might use an airport code from an interaction event to look up more information about that airport - such as its geographic location.
The following is true of all definition data:
- The data originated from a non-xDB system, such as a Content Management server or a CRM.
- A single defintion can have data from multiple cultures.
- The data is relatively static once it has been created - for example, renaming a goal would necessitate a reporting database rebuild.
Use the Reference Data Client API to access the Reference Data Service. There are two interfaces available:
In both cases, the concrete implementation can either be an HTTP client or a service that accesses the Reference Data Service database directly:
Do not use the Reference Data Client API to access marketing definitions such as goals, outcomes, and campaigns. Use the Marketing Operations API instead.
The Reference Data Service does not implement a locking mechanism, and there is no concurrency control. Each read operation and write operation is atomic, and the last successful write wins. This means that if you have two write operations that write to the same definition in a single batch, the first second operation to complete will win and overwrite data from the first operation.
Please submit documentation feedback to firstname.lastname@example.org.