<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Databases on maladroit.dev</title><link>https://maladroit.dev/kb/computer-engineering/databases/</link><description>Recent content in Databases on maladroit.dev</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://maladroit.dev/kb/computer-engineering/databases/index.xml" rel="self" type="application/rss+xml"/><item><title>Apache Iceberg</title><link>https://maladroit.dev/kb/computer-engineering/databases/apache-iceberg/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://maladroit.dev/kb/computer-engineering/databases/apache-iceberg/</guid><description>&lt;p&gt;Apache Iceberg is an open table format for huge, slow-changing, analytic
data-sets. Iceberg aims to support the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Schema evolution with no side effects&lt;/li&gt;
&lt;li&gt;Hidden partitioning to avoid performance penalties and user error&lt;/li&gt;
&lt;li&gt;Partition layout evolution as data and patterns evolve over time&lt;/li&gt;
&lt;li&gt;Time travel to reproduce historical queries&lt;/li&gt;
&lt;li&gt;Version rollback to correct problems by resetting to a known good state&lt;/li&gt;
&lt;li&gt;Readers isolated from concurrent writes&lt;/li&gt;
&lt;li&gt;Writers add and remove files atomically&lt;/li&gt;
&lt;li&gt;Planning and scanning takes &lt;code&gt;O(1)&lt;/code&gt; and is not impacted by table size&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Because Iceberg has been designed for large data-sets it can be used in
production where a single table is measured in petabytes. Iceberg is also
designed to solve correctness problems in eventually-consistent cloud object
stores. It is cloud platform agnostic, table changes are atomic so readers never
see partial changes, and concurrent writers when experiencing conflicts will
retry to ensure updates are compatible.&lt;/p&gt;</description></item></channel></rss>