SPIKE: Investigate mechanism for determining drift between Zuora and Local data
Problem
In Phase 2: Implement Zuora Cache Sync and Backfill (&13630), we are building mechanisms for backfilling and syncing Zuora Subscription data locally in CDot. In CDot, we'd like to start using the data stored locally rather than querying from Zuora. We have to trust the local data is accurate. In order to build this trust, we need to minimize problems syncing between these systems, build in redundancies for when syncing fails, and finally have tools for determining the health of the sync.
In the architecture review meeting from 2024-05-15 (agenda doc), we discussed that it might be useful to have a mechanism for determining drift between Zuora data and local data.
Proposal
The purpose of this issue is to investigate ways to have insight into the drift (if any) between Zuora and local CDot data. Some ideas to consider:
- A routine (daily?) job that queries for the most recently updated Subscriptions and ensure they have been updated in CDot. The same could be done for Rate Plans, Rate Plan Charges, and Rate Plan Charge Tiers.