Databases
Database Read Model Cleanup: Retire Projections After Product Flows Move
Database read model cleanup begins when projections, denormalized tables, cache-backed views, or event-sourced query models outlive the product flow that originally needed fast reads.
The useful output is a read model retirement record with producer lineage, reader evidence, pause result, rebuild path, and final drop decision. Keep the review concrete: Stop producers or readers before dropping the projection table, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when removing a projection still used by reports, support tools, or old clients.
Key takeaways
- Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
- Use one reporting cycle plus the longest replay, client-support, and dashboard-use window before deciding that “quiet” means “unused.”
- Prefer reversible changes first when removing a projection still used by reports, support tools, or old clients is still plausible.
- Leave behind a read model retirement record with producer lineage, reader evidence, pause result, rebuild path, and final drop decision so the next review starts with context.
- Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.
Map Producers and Readers
Start with one read model family across event topics, projection jobs, materialized tables, API readers, BI dashboards, support tools, and rebuild runbooks. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.
| Field | Why it matters |
|---|---|
| Owner | Cleanup needs a person or team that can accept the decision |
| Current purpose | A short reason to keep the item, written in present tense |
| Last meaningful use | read/write activity, size, query plans, job dependencies, and retention rules |
| Dependency evidence | database metrics, query logs, application references, and reporting schedules |
| Risk if wrong | The outage, data loss, access failure, or rollback gap the review must avoid |
| Next action | Keep, reduce, archive, disable, remove, or investigate |
Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.
Read Model Evidence
The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For database read model cleanup, collect enough evidence to answer that without relying on naming conventions.
| Check | What to look for | Cleanup signal |
|---|---|---|
| Producer lineage | Events, CDC streams, backfills, projection workers, and schema versions | No active producer updates the read model |
| Read consumers | API routes, dashboards, exports, support tools, notebooks, and old clients | No current consumer reads the projection |
| Freshness and drift | Last update time, lag, row count, checksum, and comparison with source of truth | The projection no longer reflects current product reality |
| Rebuild path | Replay topic, source tables, migration job, idempotency, and rollback owner | The model can be restored if the removal is wrong |
Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.
If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.
Example Evidence Check
Map projection producers and readers before pausing refresh jobs or dropping read-model tables.
SELECT read_model, last_refreshed_at, source_stream, owner
FROM read_model_inventory
WHERE read_model = 'account_summary_v1';
SELECT consumer_name, last_read_at, query_source
FROM read_model_consumers
WHERE read_model = 'account_summary_v1'
ORDER BY last_read_at DESC;Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.
Pause Refresh Before Drop
Use the least permanent move that proves the decision. In database read model cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.
- Stop producers or readers before dropping the projection table.
- Pause refresh or replay jobs during a monitored window.
- Archive schema and rebuild notes for one release after final removal.
Track the cleanup candidate with a simple priority score:
| Score | Good sign | Bad sign |
|---|---|---|
| Impact | Meaningful spend, risk, toil, noise, or confusion disappears | The item is cheap and low-risk but politically distracting |
| Confidence | Owner, purpose, and dependency path are understood | The team is guessing from age or name |
| Reversibility | Restore, recreate, re-enable, or rollback path exists | Deletion would be the first real test |
| Prevention | A rule can stop recurrence | The same pattern will return next month |
Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.
Projections That Still Feed Users
Some cleanup candidates are supposed to look quiet. Do not rush these cases:
- Read models used by support tools, month-end reports, or old mobile clients.
- Projections that act as a recovery shortcut when the source of truth is slow to query.
- Event streams whose replay window is shorter than the cleanup review.
For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.
Run the Projection Retirement
Run database read model cleanup as a decision review, not an open-ended hygiene project.
- Pick the narrow scope and export the candidate list.
- Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
- Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
- Apply the least permanent useful change first.
- Watch the signals that would reveal a bad decision.
- Complete the final removal only after the review window closes.
- Save a read model retirement record with producer lineage, reader evidence, pause result, rebuild path, and final drop decision.
For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.
Declare Read Model Consumers
Prevention should change the creation path, not just the cleanup path. For database read model cleanup, the useful prevention fields are data owner, retention policy, recreate path, and review date. Make those fields part of normal creation and review.
- Create read models with owner, source of truth, consumers, freshness target, and retirement trigger.
- Alert on projections with no readers or no successful refresh.
- Retire read models as part of product-flow migrations, not months later.
The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.
Example Decision Record
Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.
| Field | Example entry for this cleanup |
|---|---|
| Candidate | Stale read models in event-driven data systems |
| Why it looked stale | Low recent activity, unclear owner, or no current consumer after the first review |
| Evidence checked | Producer lineage, Read consumers, and owner confirmation |
| First reversible move | Stop producers or readers before dropping the projection table |
| Watch signal | The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong |
| Final action | Keep, reduce, archive, disable, or remove after one reporting cycle plus the longest replay, client-support, and dashboard-use window |
| Prevention rule | Create read models with owner, source of truth, consumers, freshness target, and retirement trigger |
This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.
FAQ
How often should teams do database read model cleanup?
Use one reporting cycle plus the longest replay, client-support, and dashboard-use window for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.
What is the safest first action?
The safest first action is usually ownership repair plus evidence collection. After that, stop producers or readers before dropping the projection table. That creates a visible test before permanent deletion.
What should not be removed quickly?
Do not rush anything connected to read models used by support tools, month-end reports, or old mobile clients. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.
How do you make the decision useful later?
Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.