<story><title>Insights after 11 years with Datomic [video]</title><url>https://www.youtube.com/watch?v=YSgTQzHYeLU</url></story><parent_chain></parent_chain><comment><author>clusterhacks</author><text>Several comments mention the data immutability of Datomic as a plus and I just wanted to say you can totally make a plain-old-RDBMS table append-only and get those benefits. I&amp;#x27;m sure this is commonly done.&lt;p&gt;I did it with a timestamp on the tables that was captured at insert time. All reads were against views of the tables that were defined such that the only tuples returned were the &amp;quot;most recent&amp;quot; tuples by appropriate data fields and max(timestamp). &amp;quot;Deleted&amp;quot; records were just indicated by a flag.&lt;p&gt;This preserved the ability see the full history for a tuple from creation, all mutations, all the way to deletion. This scaled reasonable well up to low millions of tuples on a normal, single database server. But it was for an internal project, so the number of clients hammering at it was quite low.</text></comment>
<story><title>Insights after 11 years with Datomic [video]</title><url>https://www.youtube.com/watch?v=YSgTQzHYeLU</url></story><parent_chain></parent_chain><comment><author>geokon</author><text>Relevant blog I found interesting: (Datalevin)&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;yyhh.org&amp;#x2F;blog&amp;#x2F;2024&amp;#x2F;09&amp;#x2F;competing-for-the-job-with-a-triplestore&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;yyhh.org&amp;#x2F;blog&amp;#x2F;2024&amp;#x2F;09&amp;#x2F;competing-for-the-job-with-a-t...&lt;/a&gt;&lt;p&gt;From the perspective of someone not familiar with the topic. And I touches on performance</text></comment>