conv.

All stories
TechRunning 1h

Shayon Publishes Technical Deep Dive on Database Write Latency Tradeoffs

Developer examines how storage engines balance write speed against durability by moving computational work to different system layers.

3 items68 engagement22 comments PressHacker NewsMastodon

Conversation activity · last 24 hours peak 2/hr

Peak 2 items in one hour at Aug 9, 11 AM; 3 items over 24 hours Aug 9, 11 AM — 2 itemsAug 9, 12 PM — 1 itemAug 9, 1 PM — no itemsAug 9, 2 PM — no itemsAug 9, 3 PM — no itemsAug 9, 4 PM — no itemsAug 9, 5 PM — no itemsAug 9, 6 PM — no itemsAug 9, 7 PM — no itemsAug 9, 8 PM — no itemsAug 9, 9 PM — no itemsAug 9, 10 PM — no itemsAug 9, 11 PM — no itemsAug 10, 12 AM — no itemsAug 10, 1 AM — no itemsAug 10, 2 AM — no itemsAug 10, 3 AM — no itemsAug 10, 4 AM — no itemsAug 10, 5 AM — no itemsAug 10, 6 AM — no itemsAug 10, 7 AM — no itemsAug 10, 8 AM — no itemsAug 10, 9 AM — no itemsAug 10, 10 AM — no items 2 items · 11 AM
Aug 10

Summary, timeline and people extracted by Claude from 3 items across 3 sources · 21h ago. Quotes are verbatim.

Shayon published a technical article analyzing the fundamental tradeoff in storage engine design: the choice of when to return success to a client on a write operation determines both latency and what failures the data can survive. The piece examines memory writes versus local SSD durability versus remote replication, showing how each choice moves work and risk elsewhere in the system.

  • Write speed and durability are coupled; faster returns mean accepting more failure scenarios, slower returns require more replication/synchronization.
  • Storage systems distribute work across memory, local SSDs, remote storage, and database replicas; choosing where to wait determines which failures are survivable.
  • Object storage with write-ahead logs offers a design pattern where the storage service owns durable copies while compute scales independently.

How it unfolded

  1. Report Article shared to Mastodon via RSS

    The article was cross-posted to Mastodon by news.ycombinator.com@rss-parrot.net, extending its reach to another platform.

  2. Event Article published on Hacker News

    Shayon published 'Every fast write moves work somewhere else' on his blog and posted it to Hacker News, where it gained 8 points and 1 comment.

What people are saying verbatim

“Every storage engine has to decide what must finish before it tells a client that a write succeeded.”

Shayon · shayon.dev blog post · Aug 8

“Those choices move latency and durability together because returning after memory is fast, but a machine crash can lose the write.”

Shayon · shayon.dev blog post · Aug 8

“So when I see a very fast number for an operation, I want to know which operation pays for it, what can still be lost after success, and how much unfinished cleanup the system can tolerate.”

Shayon · shayon.dev blog post · Aug 8