Write-Ahead Logs on S3: Compatibility Is Not Performance

Write-Ahead Logs on S3: Compatibility Is Not Performance(blog.trylle.com)

60 points by Xlab 10 days ago | 5 comments

> Its asterisk is structural: it is explicitly zonal — a single Availability Zone.

hi claude

Xlab 10 days ago | |

Fun fact: after spending 20+ hours during weekend on waltier, running all suites, I was so burned out that I just yolod almost full article via fable.

Supposed to be a hand-made blog post but I had no hands left yesterday ;)

catchnear4321 10 days ago | | |

i-know-the-feeling.meme

Xlab 10 days ago |

Following a hot topic of putting WAL on S3, initiated by Cursor blog post.

We ran an identical CAS write-ahead-log workload against AWS S3, S3 Express One Zone, Tigris, and Cloudflare R2.

Benchmark results available.

fgsbhsbsbdzs 10 days ago |

Amazing