Data aging is the action of removing table rows from the frontend while preserving them in the backend. This can be used to control main memory usage in the solidDB^® frontend database by deleting unnecessary data, while preserving the data in the backend database.

The Universal Cache data aging solution is application driven. Applications control what data is to be aged and perform the aging, that is, remove the unnecessary data from the frontend database.

The rules of aging vary from application to application. To use data aging effectively, design the subscriptions and table mappings in such a way that data that has been aged in the frontend database is not propagated back to the frontend database during subsequent refreshes or mirroring from the backend database to the frontend database.