Feature Store  ·  View 16 of 21  ·  Operations

Definition Promotion Pipeline

One gate carries the parity guarantee: a definition that compiles only one of its two plans never reaches the registry.

Editable source SVG draw.io All views
Author Definition PR GitHub Local compile Build Compiler both plans or fail Duplicate detector Contract lint types, nulls, range Gates Both plans compile? Owner approval? Backfill in budget? Promote Registry publish new version experimental → production Environments Staging feature store 1% traffic shadow Production ≤ 30 min from merge rejected over budget shadow first Definition Promotion Pipeline External / third party Application we own Security / platform Decision point failure / alternate batch A definition that compiles only one of the two plans never reaches the registry. That single gate is the parity guarantee. v 1.0 · owner Data Platform Architecture · date 2026-09

Decisions

  • The compile-both-plans gate is the parity guarantee, mechanised. Everything else in this pipeline is hygiene by comparison.
  • The backfill budget is estimated and gated before merge, so cost is a review comment rather than an invoice.
  • Duplicate detection runs at registration and requires the author to adopt, differentiate or override with a reason. Reuse that depends on goodwill does not happen.

Assumptions

  • Merge to readable-online ≤ 30 min for streaming, ≤ 1 cadence cycle for batch.
  • New definitions shadow in staging against 1% of production traffic before promotion to production lifecycle state.

Risks

  • A gate that is slow is a gate that gets bypassed. If the 30-minute target slips, teams will compute features in their own services and the platform's central claim quietly stops being true.
◀  Deployment Architecture All views Observability  ▶
Solution Architecture v1.0 · Amazon Web Services · Data Platform Architecture · 2026-09 · 21 views · 14 architecture decision records16-definition-promotion-pipeline