Data rules¶
Code: data
Total rules: 19
Rules¶
ECO-DAT-CACHE-001 — Missing cache for repeated expensive lookup¶
The same expensive query, API call, or computation is performed repeatedly when results could be safely cached.
- Category: Data
- Family: Caching
- Layer: data
ECO-DAT-DATA-001 — Duplicate stored data¶
Redundant data increases storage footprint and cost.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-002 — Missing retention policy¶
No TTL/lifecycle policy causes unbounded data growth.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-003 — Large unused indexes¶
Unused indexes waste storage and slow writes.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-004 — Logs stored indefinitely¶
Indefinite log retention increases storage and cost without clear value.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-005 — Full table scans without index¶
Full scans increase CPU, IO, and latency for queries.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-006 — Excessive replication factor¶
High replication increases storage and write amplification.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-007 — No partitioning for large tables¶
Large tables without partitioning lead to expensive queries and maintenance.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-008 — Storing ephemeral data permanently¶
Ephemeral data kept forever becomes waste by default.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-009 — No archival tier strategy¶
Lack of archival tiering keeps costs and energy higher than necessary.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-010 — Overly aggressive replication across regions¶
Cross-region replication can add cost and complexity beyond needs.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-011 — Lack of compression in object storage¶
Uncompressed objects waste storage and bandwidth.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-012 — Unbounded analytics queries¶
Unbounded queries cause runaway compute and unpredictable cost.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-013 — No data lifecycle governance¶
Lack of lifecycle governance leads to perpetual growth and shadow datasets.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-014 — Stale feature flags accumulating¶
Feature flags left indefinitely add complexity and runtime overhead.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-DATA-015 — Shadow data stores outside governance¶
Unofficial copies create duplicated storage and compliance risk.
- Category: Data
- Family: Data
- Layer: data
ECO-DAT-SER-001 — Repeated serialization/deserialization chain¶
Data is repeatedly converted between formats within the same request or processing path.
- Category: Data
- Family: Serialization
- Layer: data
ECO-OBS-LOG-002 — Large payload logging¶
Application logs capture full request, response, or message bodies where summaries or identifiers would be sufficient.
- Category: Observability & Telemetry
- Family: Logging
- Layer: data
ECO-OBS-METRIC-001 — High-cardinality metric explosion¶
Metrics include unbounded labels such as user IDs, request IDs, or raw paths, causing storage and query amplification.
- Category: Observability & Telemetry
- Family: Metrics
- Layer: data