Simplified Sliding Sync
summary
Slide-based room sync moves heavy logic out of the server: the old experimental MSC-3575 proxy flow (one new server, one new client, two new apps, one new sync mechanism) proves fast but brittle and costly, so it is replaced by MSC-4186 implemented in Synapse 1.14 and by extracting encryption and notifications to new endpoints (sliding_sync2 e2e and sl_context). Sorting and filtering now happen client-side, the SDK exposes a detection API and a reactive observable map for ranges and background growth, Element X auto-migrates, and the proxy is being deprecated.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 0:45What is sliding sync
- 2:57Debugging cycle and testing
- 5:24Sliding sync principles
- 7:56Request and response in action
- 9:43Client range API flexibility
- 11:06Need for simplification
- 13:54Simplified sliding sync proposal
- 14:58Server load and new endpoints
- 15:42Reactive programming in SDK
- 17:08Conclusion and future
- 17:30Q&A session
related talks
18mLeading edge: Sync solutions for connecting offline-apps
53mAppSync: Build real-time app experiences with modern GraphQL APIs
27mFrom Thundering Herd to Zero Outages: Building Reliable Inventory Sync
01h 20mEfficient Client-Server Communication with Differential Synchronization and JSON Patch
17mSyncing stores using socket streams
31mDecoupled, Not Disconnected: State and Sync in Micro-Frontends
34mBuilding a Sync Engine in Clojure
40mCroquet. A Unique Collaboration Architecture