Sync Mechanics Deep Dive

Module Overview

This module covers the core mechanics of how SyncApp synchronises data between a PMS and the Weave platform, from full and partial sync strategies through the Standard Batch Syncer pipeline to hands-on debugging of on-prem and cloud PMS integrations using RPCs.

Why This Module Matters

Engineers building or maintaining integrations must know exactly when a full sync fires versus a partial sync, how the Batch Syncer detects record changes via hashing, and how to diagnose connectivity and data issues across both on-prem and cloud PMS environments. Without this foundation, troubleshooting sync failures or optimising sync frequency becomes guesswork rather than a systematic process.

Learning Goals

• Explain the difference between full sync and partial sync, including the date anchor used to trigger a full fetch
• Describe the per-record pipeline the Standard Batch Syncer executes — extract, transform, Unicode clean, hash, compare — and identify where changes are detected
• Distinguish push-type entities from standard entities and articulate why push types are always fetched in full
• Identify the RPC tools available for debugging SyncApp instances and apply them to inspect connectivity and sync state on on-prem PMS deployments such as Eaglesoft 18
• Compare the connectivity model for an on-prem PMS running inside a VM versus a cloud-hosted PMS like NXT and explain the implications for debugging
• Determine from a given sync scenario whether a partial or full sync is appropriate and what data the syncer will request from the PMS

Lessons