Module 07 · Week 2
Weave Integrations Academy
SyncApp Architecture — High Level
Architecture Overview, ICPA, SyncApp API, and Write-backs
Module Overview
This module provides a comprehensive architectural view of the entire SyncApp ecosystem — covering both the data ingress path (PMS → SyncApp → Data Service) and the egress/write-back path (Weave UI → SyncApp → PMS). You'll learn about the ICPA proxy, HTTP streaming, the SyncApp API as the core ingress service, and the V2/V3 write-back architecture including NSQ, WebSocket connections, and the SyncApp Manager.
Why This Module Matters
Most engineers understand SyncApp as a data puller. This module reveals the full bidirectional architecture — including the services SyncApp depends on (ICPA, SyncApp Manager, SyncApp API) and how write-backs flow back to the PMS. This context is essential for any work that touches write-back features.
Learning Goals
- Describe the full SyncApp architecture including ICPA proxy and monitoring (Prometheus/Grafana)
- Explain HTTP streaming and why it's more efficient than standard REST for data sync
- Understand the SyncApp API as a glorified proxy service between SyncApp and Data Service
- Explain write-back V2 (MSQ-based) vs V3 (library-based) architecture
- Describe the SyncApp Manager's role in managing WebSocket connections for write-backs