Introduction to SyncApp
Why This Matters
SyncApp is your primary domain. Understanding it as a data pipeline — pulling from PMS database, transforming, pushing to Weave database — is the mental model you'll use every day.
What You'll Learn
- SyncApp's bidirectional role: pulling data from PMS and also writing data back (for write-back features)
- The two-database architecture: PMS database on one side, Weave database on the other
- How SyncApp sits between these two databases as the transformation layer
- Why SyncApp is described as the gateway for all PMS-Weave interactions
- The simplified architecture diagram: PMS DB → SyncApp → Weave DB
Watch Video
Open in Google Drive
💡 Open in Drive for AI-powered transcript search and summaries
Lesson Summary
SyncApp is the service that bridges two separate databases: the PMS database (which the customer's practice management software reads from) and the Weave database (which the Weave UI reads from). SyncApp runs continuously, pulling data from the PMS database, transforming it, and pushing it into Weave's database. The double-sided arrow in the architecture diagram reflects that SyncApp also supports write-backs for features like Forms and Online Scheduling — data flows both ways through SyncApp.
Key Concepts
SyncApp Architecture
PMS Database
Weave Database
Bidirectional Sync
Data Pipeline
Transformation Layer
Key Takeaways
01SyncApp is the only service that communicates between the PMS world and the Weave world — everything flows through it
02The PMS database and Weave database never communicate directly — SyncApp is always the intermediary
03SyncApp's bidirectional arrow means it handles both read (pull) and write (push) operations
04Think of SyncApp as a stateless transformer: it reads, transforms, and writes — but doesn't own the data