reverse-etl-from-a-warehouse

Use it when

• Values are computed in a warehouse (a score, a segment, a lifetime value) and people need them in an app.
• Each warehouse row matches one app record by a key, such as the app's record id or an email.
• A refresh every 15 minutes to every 24 hours is enough (Data Sync Frequency 450 to 43200 seconds).

Why this design

Advantages:

• A one-way sync from the warehouse cannot overwrite the warehouse.
• A view works as the source, and views are one-way by nature.
• The sync's rate limit keeps writes under the app's API limit.

Trade-offs:

• Each changed row is a write in the app; recomputing all scores each night can update every record.
• The key must exist on both sides; rows without a matching record become new records.