giving sync

thoughts.md

Current problems

1. If Rock is offline a transaction won't ever get sent to Rock
2. If Rock has an error, the transaction won't get created fully in Rock
3. If two servers pick up the new db entry at once, you can have duplicates
4. Rock's NMI sync seems to be problematic (not pulling down transactions, etc)
5. Error reporting doesn't exist
6. Manually editing / creating schedules or transactions in Rock is difficult / impossible

This problem manifests in a lot of ways, the most common issue is missing data from a person's giving history. This is typically due to schedules missing and not syncing.

Proposed solution

1. Make it easy to create transactions / schedules in Rock without charging (i.e. from data in NMI, manually entered)
2. Decouple give methods from meteor (move to heighliner) so they can be easily tested
3. Create job system to process transactions
4. Use Ids to prevent duplication
5. Send errors to sentry
6. Turn of Rock's sync and write custom one for heighliner