Rebuilding Linear’s delta sync read path
linear.app · 1,425 words · saved by 1 readers
How we use Turbopuffer to keep catch-up latency predictable across more than 20 TB of sync actions.
Linear is a local-first application. Each client maintains a local database so that creating an issue, changing its status, or navigating a workspace doesn’t require a network round trip. That makes the app feel immediate, but the tradeoff is that a client returning online needs a way to catch up, fast. Rather than download the entire workspace again, the client sends a checkpoint containing the ID of the last change it applied. Delta sync uses that checkpoint to retrieve only what has changed in the meantime. Some of our largest workspaces produce close to one million sync actions per…
saved by
related reading
- How's Linear so fast? A technical breakdownperformance.dev
- turbopufferturbopuffer.com
- From monolith to Lakebase to LTAP: rethinking the database from storage up | Databricks Blogdatabricks.com
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- DeltaNet Explained (Part I) | Songlin Yangsustcsonglin.github.io
- Exploring versions of the Postgres logical replication protocolblog.peerdb.io
- Delta | A Multiplayer Environment for Coding with Agentsdelta.dev
- turbopuffer: fast search on object storageturbopuffer.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- learning-notes/books/designing-data-intensive-applications.md at master · keyvanakbary/learning-notes · GitHubgithub.com
- Parallelizing Linear Transformers with the Delta Rule over Sequence Lengtharxiv.org
- Patching the PostgreSQL JDBC Driverengineering.zalando.com