Architecting for performance: Integrating Optimizely and Microsoft Dynamics 365 for the MCG
Separate page reads from background synchronisation. Add retries, deduplication and alerts, and provide an understandable fallback when the business system slows down.
Putting system integration into practice
Define authoritative data, field mappings and update direction before requests. Duplicates, delay and partial failure require deduplication, retries and traceable records.
Checking the result
Test duplicates, downtime and resumed synchronisation for lost or overwritten data. Public messages should explain status without exposing internal information.
