<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Slides on jayeffsee</title><link>https://www.jayeffsee.com/slides/</link><description>Recent content in Slides on jayeffsee</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.jayeffsee.com/slides/index.xml" rel="self" type="application/rss+xml"/><item><title>From warehouse to data contracts</title><link>https://www.jayeffsee.com/slides/data-platform/</link><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.jayeffsee.com/slides/data-platform/</guid><description>&lt;h1 id="from-warehouse-to-data-contracts"&gt;&#10; From warehouse to data contracts&#10; &lt;a class="heading-link" href="#from-warehouse-to-data-contracts"&gt;&#10; &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;&#10; &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;&#10; &lt;/a&gt;&#10;&lt;/h1&gt;&#10;&lt;p&gt;A new approach to our data platform&lt;/p&gt;&#10;&lt;p&gt;~10 minutes · then questions&lt;/p&gt;&#10;&lt;p&gt;Note: [0:15] Set the frame. One idea for the whole talk: the way we get data in doesn&amp;rsquo;t scale with a central team, so we&amp;rsquo;re changing who does the work and giving them a pattern to follow.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="a-very-short-history"&gt;&#10; A very short history&#10; &lt;a class="heading-link" href="#a-very-short-history"&gt;&#10; &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;&#10; &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;&#10; &lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Data warehouse&lt;/strong&gt; - structured, central, trusted. But one team models everything, and every new source waits in their queue.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Data lake&lt;/strong&gt; - store anything, cheaply. But no schema, no transactions: the &amp;ldquo;data swamp&amp;rdquo;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Lakehouse&lt;/strong&gt; - open table formats (Iceberg, Delta, Hudi) bring warehouse guarantees to cheap lake storage.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Data mesh and data contracts&lt;/strong&gt; - owners publish their own data under an agreed contract.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;Note: [1:00] Each step fixed one problem and left another. The last one is about &lt;em&gt;who does the work&lt;/em&gt;, and that&amp;rsquo;s where this talk lands.&#10;Dates if asked: Iceberg started at Netflix in 2017 (Apache top-level 2020). Data mesh article 2019. &amp;ldquo;Lakehouse&amp;rdquo; popularised 2020-21 (CIDR 2021 paper). Data contracts take shape from 2021; Open Data Contract Standard 2023.&#10;Mesh is about who owns data. Lakehouse is about where it lives. Contracts are how owners agree on it. They&amp;rsquo;re complementary, not successive.&lt;/p&gt;</description></item></channel></rss>