<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ddia on Akshay Deshpande</title>
    <link>https://akshayd-dev.pages.dev/categories/ddia/</link>
    <description>Recent content in Ddia on Akshay Deshpande</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://akshayd-dev.pages.dev/categories/ddia/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Encoding: From the POV of Dataflow paths</title>
      <link>https://akshayd-dev.pages.dev/posts/encoding-from-the-pov-of-dataflow-paths/</link>
      <pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/encoding-from-the-pov-of-dataflow-paths/</guid>
      <description>&lt;p&gt;When studying Chapter 4 of &lt;em&gt;&lt;strong&gt;Designing Data-Intensive Applications&lt;/strong&gt;&lt;/em&gt; (Encoding and Evolution), I quickly encounters a level of granularity that seems &lt;em&gt;mechanical&lt;/em&gt;: binary formats, schema evolution, and serialization techniques. Yet behind this technical scaffolding lies something conceptually deeper. Encoding is not merely a process of serialization; it is the very grammar through which distributed systems express and interpret meaning. It is the act that allows a system’s internal thoughts — the data in memory — to be externalized into a communicable form. Without it, a database, an API, or a Kafka stream would be nothing but incomprehensible noise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>[DDIA Book] : Data Models and Query Languages</title>
      <link>https://akshayd-dev.pages.dev/posts/ddia-book-data-models-and-query-languages/</link>
      <pubDate>Tue, 10 Oct 2023 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/ddia-book-data-models-and-query-languages/</guid>
      <description>&lt;p&gt;[Self Notes and Review]:&lt;/p&gt;
&lt;p&gt;This is a second writeup in the series of reading DDIA book and publishing my notes from the book.&lt;br&gt;
The first one can be found &lt;a href=&#34;https://performanceengineeringin.wordpress.com/2023/07/05/reliable-scalable-and-maintainable-application/&#34;&gt;here&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This particular article is from the second chapter of the book. Again, these are just my self notes/extracts and treat this more like an overview/summary. Best way is to read the book in itself.&lt;/p&gt;
&lt;p&gt;This chapter dwells in to the details of: the format in which we write data to databases and mechanism by which we read it back.&lt;/p&gt;</description>
    </item>
    <item>
      <title>[DDIA Book]: Reliable, Scalable and Maintainable Application</title>
      <link>https://akshayd-dev.pages.dev/posts/reliable-scalable-and-maintainable-application/</link>
      <pubDate>Wed, 05 Jul 2023 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/reliable-scalable-and-maintainable-application/</guid>
      <description>&lt;p&gt;[Self Notes and Review]:&lt;/p&gt;
&lt;p&gt;This is a new series of publications where I am publishing my self notes/extracts from reading the very famous book - DDIA (Designing Data-Intensive Applications) by Martin Kleppmann.&lt;/p&gt;
&lt;p&gt;This particular article is from the first chapter of the book. Again, these are just my self notes/extracts and treat this more like an overview/summary. Best way is to read the book in itself.&lt;/p&gt;
&lt;p&gt;Side note: I am a terribly slow and repetitive reader. The update between chapters might take weeks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
