Topic

Data Expiration

1 post about Data Expiration. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

MongoDB
Enhancing Atlas Online Archive With Data Expiration And Scheduled Archiving
Atlas Online Archive moves infrequently accessed data from a cluster to a MongoDB-managed object store while enabling unified queries across both tiers. A new data expiration feature lets users set a deletion threshold for archived data, configurable from 7 to 9,125 days through the Atlas UI or Admin API, and rules can be edited after creation; previously, the only way to remove data was deleting the entire archive. Once data is deleted from the archive, it cannot be recovered, so rules must be defined carefully. Scheduled archiving addresses performance concerns by allowing users to define a recurring window—daily, weekly, or monthly—with a minimum duration of two hours, replacing the previous five-minute interval that could overload clusters during peak times. Users can edit the archive rule to specify both when to archive and when to delete, and both features are in preview to improve operational efficiency for Atlas customers.

The best engineering reads, once a week.

Topic

1 post about Data Expiration. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

MongoDB
Enhancing Atlas Online Archive With Data Expiration And Scheduled Archiving
Atlas Online Archive moves infrequently accessed data from a cluster to a MongoDB-managed object store while enabling unified queries across both tiers. A new data expiration feature lets users set a deletion threshold for archived data, configurable from 7 to 9,125 days through the Atlas UI or Admin API, and rules can be edited after creation; previously, the only way to remove data was deleting the entire archive. Once data is deleted from the archive, it cannot be recovered, so rules must be defined carefully. Scheduled archiving addresses performance concerns by allowing users to define a recurring window—daily, weekly, or monthly—with a minimum duration of two hours, replacing the previous five-minute interval that could overload clusters during peak times. Users can edit the archive rule to specify both when to archive and when to delete, and both features are in preview to improve operational efficiency for Atlas customers.

The best engineering reads, once a week.