That depends on the requirements you develop for a hybrid-data solution.
Ideally, all Airtable data is captured in the sustainable and near-limitless cavern of the selected [alternate] database system, and then – depending on use cases,
user needs, and other process requirements – data is either archived based on metrics applied via the Airtable API, or it is paged into and out of Airtable to fit certain operational objectives.
This is neither easy nor is it a trivial matter. It requires carefully crafted integration based on automated and intelligent processes that make Airtable seem like it has limitless data storage and accessibility.