DynamoDB reaping
Last updated 2026-06-14
Definition
DynamoDB reaping auto-expires old rows so Quri’s store stays lean. Records that no longer need to live — short-lived caches, aged chat transcripts — get a time-to-live stamp, and the database deletes them automatically once that time passes. You keep the data that matters and pay nothing to store rows that have outlived their use.
How to do this in Quri
- Use Quri normally — short-lived records are stamped with an expiry as they are written.
- The database removes each row automatically once its time-to-live passes.
- Notice that aged caches and old transcripts disappear without any cleanup work from you.
- Rely on it to keep the store small, fast to query, and cheap to run.
Frequently asked
- Will reaping delete data I still need?
- No. Only records meant to be short-lived — caches and aged transcripts — carry an expiry. Data you rely on is not stamped to expire, so reaping clears clutter without touching what matters.
- Why expire rows automatically?
- Keeping rows that have outlived their use slows queries and costs money to store. Letting the database reap them on a time-to-live keeps the store lean, so reads stay fast and Quri stays cheap to run.