How’s Linear so fast? A technical breakdown

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get home appliances delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Linear’s speed stems from using an in-browser database (IndexedDB), a custom sync engine for background updates, and optimized UI responsiveness. This approach minimizes network delays, making updates feel instantaneous.

Linear’s issue updates take just a few milliseconds, a stark contrast to the 300ms typical of traditional CRUD applications. This speed is driven by their innovative use of in-browser databases, custom sync engines, and UI optimizations, making their app feel native and highly responsive.

Linear’s core performance advantage comes from storing its database directly in the browser using IndexedDB, allowing local mutations to be applied instantly without waiting for network requests. When users update an issue, the change is reflected immediately in the UI via in-memory state, with background processes asynchronously syncing data to the server. This eliminates loading spinners and delays, creating a seamless experience.

Their custom sync engine is designed from day one to batch and manage data transmissions efficiently. When a user makes a change, it updates the local store instantly, then queues the update for background transmission, ensuring the interface remains responsive. This approach contrasts with typical web apps that wait for server confirmation before updating the UI.

Linear’s stack is minimalistic, built on React, TypeScript, MobX, and PostgreSQL, with additional tools like Redis for event management and Cloudflare Workers for edge processing. They also prioritize client-side rendering, which, combined with their architecture, results in near-instant updates and a fluid user experience.

Why It Matters

This technical approach demonstrates a paradigm shift in web app performance, emphasizing local data management and background syncing to achieve near-instantaneous updates. For users, this translates into faster workflows and less frustration with loading states. For developers, it offers insights into building highly responsive applications without relying on complex or heavy frameworks, potentially influencing future web development practices.

Background

Traditional web apps depend on server round-trips for data updates, often causing visible delays. Linear’s approach, pioneered by their early focus on a local-first architecture, leverages IndexedDB for persistent local storage and a custom synchronization process. This strategy was discussed publicly by co-founder Tuomas in 2024, emphasizing their commitment to performance from the outset. Their stack choices reflect a preference for simplicity and efficiency, avoiding more complex or resource-heavy frameworks.

“Literally the first lines of code that I wrote was the sync engine, which is very uncommon to what you usually do when you’re a startup.”

— Tuomas, Linear co-founder

What Remains Unclear

It is not yet clear how Linear handles complex conflicts or data consistency issues across multiple clients, or how their architecture scales with larger data sets and user bases. Specific implementation details of their sync engine remain proprietary.

What’s Next

Further technical disclosures from Linear or independent audits could clarify their conflict resolution strategies. Additionally, observing how their architecture adapts to scaling and new features will be key to understanding its long-term viability.

Key Questions

How does Linear achieve such fast issue updates?

By storing data locally in IndexedDB and applying mutations instantly in memory, then syncing asynchronously with a custom engine, Linear eliminates network delays from the user experience.

Can other web apps replicate Linear’s performance?

Most can approximate it using optimistic updates and local storage, but Linear’s dedicated sync engine and architecture are specialized for ultra-fast responsiveness.

Does this approach affect data consistency across devices?

Details about conflict resolution are not publicly confirmed. However, their background sync likely includes mechanisms to handle conflicts, though specifics are proprietary.

What are the main technologies behind Linear’s speed?

Key technologies include IndexedDB for local storage, a custom sync engine, React and MobX for UI, and background processes managing data transmission efficiently.

Source: Hacker News