<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Storage on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/storage/</link><description>Recent content in Storage on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 14 Jul 2026 10:04:25 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/storage/index.xml" rel="self" type="application/rss+xml"/><item><title>IcefallDB: Time Travel on Plain Parquet Files</title><link>https://www.visorcraft.com/news/2026/07/icefalldb-time-travel-parquet/</link><pubDate>Tue, 14 Jul 2026 10:04:25 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/07/icefalldb-time-travel-parquet/</guid><description>&lt;p&gt;Parquet is the columnar format that ate the data lake, and for good reason: it compresses well, it reads fast, every analytics engine from DuckDB to Spark to DataFusion speaks it natively, and the files are just sitting there on disk waiting to be queried by anything that can open them, which is the same property that made SQLite appealing for a different class of problem. The catch, and it is a significant catch, is that Parquet is immutable by design, the format spec has no concept of updating a row in place, deleting a tuple, or merging two versions of a record, and the moment you need any of those operations you are in the business of rewriting files or building a layer on top that pretends mutability exists; IcefallDB is that layer, and the interesting work was making the pretension convincing enough that you stop noticing it.&lt;/p&gt;</description></item></channel></rss>