Cloud PMS and SyncApp
Why This Matters
Most modern PMSs are cloud-hosted. Understanding how SyncApp talks to a cloud PMS via APIs — and why each office gets its own SyncApp pod — is essential for understanding the scale and isolation model of the Integrations team.
What You'll Learn
- What a cloud PMS is: the PMS database lives in the cloud, accessible via REST APIs
- Why SyncApp runs on a Kubernetes pod (cloud) when the PMS is also cloud-based
- The one-SyncApp-per-office architecture: each office has its own isolated SyncApp instance
- Why this design is unconventional compared to traditional microservices but provides strong isolation
- SyncApp's role for cloud PMS: call APIs → receive data → send to Data Service (no local storage)
Watch Video
Lesson Summary
When a PMS is cloud-hosted, its data is accessible via APIs. SyncApp for cloud PMSs runs as a Kubernetes pod in Weave's cloud infrastructure. The key architectural decision: each office gets its own SyncApp instance (one-to-one mapping). This is deliberately unconventional — in typical microservices, one service handles all customers. Here, isolation is prioritized: a crash or bad data in one SyncApp doesn't affect other offices. The flow is: SyncApp pod calls PMS API → receives response → transforms data → calls Data Service API → Data Service writes to Weave DB.