Plaid sync domain improvements (#2267)

Breaks our Plaid sync process out into more manageable classes. Notably, this moves the sync process to a distinct, 2-step flow:

1. Import stage - we first make API calls and import Plaid data to "mirror" tables
2. Processing stage - read the raw data, apply business rules, build internal domain models and sync balances

This provides several benefits:

- Plaid syncs can now be "replayed" without fetching API data again
- Mirror tables provide better audit and debugging capabilities
- Eliminates the "all or nothing" sync behavior that is currently in place, which is brittle
This commit is contained in:
Zach Gollwitzer
2025-05-23 18:58:22 -04:00
committed by GitHub
parent 5c82af0e8c
commit 03a146222d
72 changed files with 3763 additions and 706 deletions

View File

@@ -1,5 +1,7 @@
one:
family: dylan_family
plaid_id: "1234567890"
plaid_id: "item_mock_1"
access_token: encrypted_token_1
name: "Test Bank"
name: "Test Bank"
billed_products: ["transactions", "investments", "liabilities"]
available_products: []