CONCEPT Cited by 1 source

Metadata Dependency Fragility

Definition

Metadata dependency fragility occurs when a system assembles its operational view of the world from multiple independent sources — each with different failure modes, update cadences, and accuracy guarantees — creating a composite that silently diverges from reality over time.

Canonical example

Netflix's legacy Casspactor (Source: sources/2026-06-19-netflix-the-evolution-of-cassandra-data-movement-at-netflix):

• To answer "which backup exists, is it complete, and what does it contain?", Casspactor queried multiple independent services.
• Metadata fell out of sync with actual backups, causing silent stale/incorrect data reads.
• A single node replacement could break data movement for an entire region because the system required all nodes to snapshot at the same clock second.

Resolution

Replace the composite with a single source of truth — in Netflix's case, reading metadata directly from the backup files stored in S3 (see patterns/s3-as-single-source-of-truth).

Seen in

• sources/2026-06-19-netflix-the-evolution-of-cassandra-data-movement-at-netflix — the primary motivator for replacing Casspactor.