Skip to main content
Source partitions mirror the exact shape of a single data source. They provide downstream applications with a low-latency view of raw resources and relationships without waiting for master data management (MDM) processing or cross-source reconciliation. Source partition data flow

Characteristics

  • Single-source scope — Each partition points to one data source and indexes only the profiles and relationships declared there.
  • Minimal transformation — Records are exposed exactly as they were ingested. Use this partition type when downstream workflows rely on source-specific semantics.
  • Fast provisioning — As soon as ingestion succeeds, resources are searchable through the partition’s collections.
  • Multiple per source — You can create several partitions for the same source, each with tailored collections or access policies.
Source partitions are ideal for operational workloads that need a direct view of upstream data. If you need deduplicated or merged entities, switch to an MDM partition.

Configuration model

Source partitions are defined through the Data Partition API with three core sections:
  • key — Unique identifier used in every partition API request.
  • modules — Enabled capabilities. Source partitions support search with the STANDARD engine.
  • source — Connects the partition to its backing data source. Set type to DATA_SOURCE, provide the source key, list the collections (profiles) to expose, and the relationships the partition should index.
{
  "key": "provider-directory",
  "modules": {
    "search": "STANDARD"
  },
  "source": {
    "type": "DATA_SOURCE",
    "key": "network-ehr",
    "collections": [
      {
        "key": "provider"
      },
      {
        "key": "office"
      }
    ],
    "relationships": [
      "locatedAt"
    ]
  }
}

Operational considerations

  • Access control — Partitions are often tied to roles or environments. Use multiple source partitions when different teams need curated slices of the same source.
  • Schema evolution — Because data is unmodified, any profile update immediately affects what downstream systems receive. Coordinate profile changes carefully.
  • Migration path — Many teams start with a source partition for rapid adoption and later add an MDM partition to serve harmonized views side-by-side.

Keep exploring

I