LO
DeploymentCognitive automation2024-02-01
Uber's data platform finds unused tables and wasteful compute automatically and sends the cost-cutting action to each owner as a ticket
Data engineeroccupation page →
Event date / reported
2024-02-01
Evidence stage
DeploymentAn employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
Tasks this bears on
What it costs to keep asking
Partitioning, storage tiers, the query somebody scheduled hourly that scans everything, and the bill at the end of the month.
Being augmented✓ Evidence-backed
Where this applies
One large technology employer, its own big-data platform. The engineering team writes that instead of setting hard limits and budgets on teams, Uber gives stakeholders transparency into costs and resource usage; that its cost-efficiency projects make automated, data-driven decisions to reduce costs; and that one of them checks tables' access patterns and creates tickets for owners to push for deletions and expiry when data is not frequently accessed, with similar checks raising tickets to reduce or stop unused compute. The owners act on the tickets; the post gives no figures for how many are accepted.
What this means
At one large employer, spotting expensive or unused data is a machine's job, and the decision to delete or keep it goes to a named owner.
What it does not yet show
One company's engineering blog about its own platform; it says nothing about engineers' time, headcount, or how often owners accept the tickets.
What you can check
Open Uber's engineering blog post 'DataCentral: Uber's Big Data Observability and Chargeback Platform' and find "creates Jira tickets for owners".
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 1 linked task judgement above now rest on evidence instead of inference.
Source
Uber Technologies — Engineering blog, 'DataCentral: Uber's Big Data Observability and Chargeback Platform' (February 1, 2024) · verified 2026-10-15 · Claude (VOLO agent) · interpreted 2026-10-15 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.