Hi everyone,
I’m currently working on a CRM system built on .NET, and we’ve started facing some data synchronization issues between internal services and external APIs.
The main challenge is that client-related data (like lead status, booking details, and document updates) is not always staying consistent across the system. In some cases, updates from one service are delayed or overwritten when another API call processes slightly later. This is becoming more noticeable as usage increases.
This is happening in a real estate setup for a project like Experion Windchants, where multiple workflows (sales, booking, and documentation) interact with the same client records at different stages.
We’re using REST APIs for communication, and most operations are handled synchronously, but a few background jobs also update records. It feels like there’s a gap in how we’re handling concurrent updates and state consistency.
I’ve been exploring whether this is more of a design issue (like missing idempotency or poor update handling) or if we should move toward a more event-driven approach. I also came across OpenZiti while looking into secure communication, but I’m not sure if that’s relevant to solving sync-level problems or just networking/security.
Has anyone dealt with similar data sync issues in a .NET-based system with multiple APIs?
How do you usually handle consistency especially when multiple services can update the same entity?
Any practical suggestions or patterns to look into would really help.
