I wrote this after seeing the same failure modes across multiple teams and metrics stacks.
The intent here isn’t to argue that high cardinality is bad but to explain the mechanical reasons unbounded cardinality shows up later as cost surprises, slow queries, and trust erosion.
Curious if others have seen similar query-time or indexing issues they have noticed.
The intent here isn’t to argue that high cardinality is bad but to explain the mechanical reasons unbounded cardinality shows up later as cost surprises, slow queries, and trust erosion.
Curious if others have seen similar query-time or indexing issues they have noticed.