On-Prem PMS and SyncApp
Why This Matters
Many of Weave's customers use legacy on-premise PMS software installed on their local machines. This is a fundamentally different deployment model that you'll encounter regularly — and it has important implications for how SyncApp runs and what happens when the office closes.
What You'll Learn
- What on-prem PMS means: the database lives on the customer's machine, not in the cloud
- Why SyncApp must run on the customer's machine for on-prem PMSs
- What happens to syncing when the customer turns off their computer (vacation, after hours)
- Why this is acceptable behavior: closed office = no new data to sync
- The architecture is identical to cloud SyncApp except for where it runs
Watch Video
Lesson Summary
On-prem PMSs store their data in a SQL database on the customer's local machine (typically Windows). Because the data never leaves the machine, SyncApp must also run on that machine to access the database. The architectural model is the same: one SyncApp per office, but instead of a Kubernetes pod, it's a process running on the customer's PC. If the office closes and turns off their computers, the SyncApp process stops — but this is acceptable because there's no new data to sync when the office is closed. The data still flows to Data Service over the internet once the SyncApp is running.