Record🤔

uri:

"at://did:plc:iwpxnj7rzdynjkkr7rxaa5is/app.bsky.feed.post/3lbpcnotias26"

cid:

"bafyreieid4uhzgvo7iv6xuk4a3twab3de6xodjpr2yembla4sk3upmd5eq"

value:

text:

"published a new blog post: Zero Disk Architecture for Databases.

This is a follow up to my previous post on Disaggregated Storage, and I share some notes on writing a database on top of S3. I've included links to existing databases that already use S3.

avi.im/blag/2024/ze..."

$type:

"app.bsky.feed.post"

embed:

$type:

"app.bsky.embed.images"

images:

• alt:

  "Zero Disk Architecture
  
  The idea is simple. Instead of writing to a storage server, we will write to S3. Thus we will not manage any storage server, rather we offload it to the smart folks at AWS. S3 meets all our requirements. As a bonus, you get infinite storage space. S3 came out in 2006 and it has proven test of time. It provides 99.999999999% (that’s elevan nines) durability and 99.99% availability guarantees. I believe the next generation of infrastructure systems will be built on zero disk paradigm.
  
  This idea is not new. In 2008, there was a research paper ‘Building a Database on S3’ - a paper way ahead of its time, with lots of interesting ideas for today’s cloud computing. The researchers experimented with storing a B-tree on S3 using SQS as a Write-Ahead Log (WAL). They also provided analysis on latency when writing to S3 and the associated costs. The paper had some flaws, like they dropped ACID properties. However, we are in 2025, and we can do better."

  image:

  

  View blob content

  $type:

  "blob"

  ref:

  $link:

  bafkreigdkccrairwzbhu6yqou3nm3lbpyrcjrml7iswfoip4ahq7ahtgoy

  mimeType:

  "image/jpeg"

  size:

  116204

  aspectRatio:

  width:

  652

  height:

  389

langs:

• "en"

facets:

• index:

  byteEnd:

  277

  byteStart:

  255

  features:

  • uri:

    "https://avi.im/blag/2024/zero-disk-architecture/"

    $type:

    "app.bsky.richtext.facet#link"

createdAt:

"2024-11-24T15:20:17.526Z"