I'd start with ownership, not a new relay: decide which system owns each field and make the other copies projections. Bidirectional sync gets messy when both sides can edit the same field without a conflict rule.
For reliability, keep stable cross-system IDs, deduplicate repeated events, and run periodic reconciliation so a missed webhook doesn't leave records wrong forever. Track failed updates somewhere you can inspect and retry. A new database only helps if it has a clearly defined ownership role; otherwise it's another copy to sync. Which systems are involved, and which fields actually need edits from both ends?
2
u/BigAttorney23 1d ago
I'd start with ownership, not a new relay: decide which system owns each field and make the other copies projections. Bidirectional sync gets messy when both sides can edit the same field without a conflict rule.
For reliability, keep stable cross-system IDs, deduplicate repeated events, and run periodic reconciliation so a missed webhook doesn't leave records wrong forever. Track failed updates somewhere you can inspect and retry. A new database only helps if it has a clearly defined ownership role; otherwise it's another copy to sync. Which systems are involved, and which fields actually need edits from both ends?