SyncApp Architecture — High Level

Module Overview

This module covers the high-level architecture of SyncApp, tracing data flow from PMS sources through supporting services (ICPA, SyncApp Manager, HTTP streaming) into the Data Service, and back out via the write-backs service. Engineers examine both deployment modes, the role of SyncApp API as the single ingress point, and how write-back operations are logged and routed.

Why This Module Matters

Every integration the team builds runs on top of this architecture — misunderstanding deployment modes, ingress routing, or write-back table structure leads to misconfigured provisioning, dropped data, and undiagnosable failures. Engineers who can trace a record from PMS to Weave UI and back are equipped to debug, extend, and own integrations end-to-end.

Learning Goals

• Explain the difference between on-prem and cloud SyncApp deployment modes and identify which PMS integrations use each
• Describe the role of ICPA as a proxy layer, including how it enforces rate limits and feeds monitoring data to Prometheus/Grafana
• Trace a data record from PMS source through SyncApp API and into Data Service via gRPC
• Identify the purpose of HTTP streaming in the architecture and how SyncApp Manager coordinates SyncApp instances
• Describe the schema of the generic_writeback_v3 table and explain what data it captures for every write-back attempt
• Map the source_tenant table's role in connecting site IDs to SourceTenantIds within the write-backs service

Lessons