Real-time sync or scheduled batches: where do you draw the line?

hgray

Not every integration needs to update immediately. A daily summary can tolerate a scheduled batch, while an operational queue may need a much shorter delay. More frequent updates can also make rate limits, troubleshooting, and reconciliation harder.

For a generic CRM-to-analytics integration, how would you decide which records need fast updates and which can wait? I would like to hear how teams define acceptable delay, communicate it to users, and handle the gap between an upstream change and its appearance in a report.

lbennett

I would define a freshness target for each use case before picking the transport. A management report and an operational alert can have different targets even if they use the same source. Show the last successful sync time, and reconcile totals periodically so a fast pipeline does not hide missing records.