Article may be outdated

This article is 8 days old. Some details may have changed since publication.

Hacker News·4 min read·hard

Every fast write moves work somewhere else

S
shayonj
Every fast write moves work somewhere else
AI Summary

This article explores the architectural trade-offs in database storage engines regarding write durability and latency. It highlights how different systems balance the speed of memory-based writes against the safety of local SSDs or remote object storage.

Every storage engine has to decide what must finish before it tells a client that a write succeeded. The quickest answer is to return after copying the bytes into memory. A local durable write waits for fdatasync() on an SSD in the database host. Keeping the write after that host disappears means waiting for a network volume, an object store, or several database servers to save their own copies.

Continue reading on Headlinne

Create a free account to read the full article.

Read full article →
technologybusiness

Get the full story

Sign up for Headlinne to unlock AI insights, political bias analysis, and your personalized news feed.

Create free account

Already have an account? Sign in