An Mvcc-Like Columnar Table on S3 with Constant-Time Deletes
Posted3 months agoActive3 months ago
shayon.devTechstory
calmpositive
Debate
20/100
Database DesignCloud StorageMvcc
Key topics
Database Design
Cloud Storage
Mvcc
The post discusses a novel columnar table design on S3 that achieves constant-time deletes using an MVCC-like approach, sparking discussion on its potential applications and trade-offs.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
4d
Peak period
5
Day 5
Avg / period
3
Key moments
- 01Story posted
Oct 6, 2025 at 12:33 PM EDT
3 months ago
Step 01 - 02First comment
Oct 10, 2025 at 9:49 AM EDT
4d after posting
Step 02 - 03Peak activity
5 comments in Day 5
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 15, 2025 at 6:24 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45493158Type: storyLast synced: 11/20/2025, 2:40:40 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
It does work with "one more file" but it's not good for performance.
Not as easy as just appending metadata to a parquet file but in the other hand, parquet was never and probably shouldn’t be designed with that functionality in mind.
The cost estimates are particularly notable: if they're right that's a cost of about $3/day for 6TB/day of written data, 2TB/day of deletes and 50K read queries.
Storing all those TBs of data in S3 is where the real cost lies. I think it costs $5520 to store 8TB*30 = 240TB in S3, and if you retain all data your monthly cost goes up by $5520 every month.
The cost isn't that bad all things considered. Hot, durable and available data ain't that cheap, especially in the cloud. Self-hosting is within an order of magnitude.