<?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>Ai on Akshay Deshpande</title>
    <link>https://akshayd-dev.pages.dev/tags/ai/</link>
    <description>Recent content in Ai 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/tags/ai/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>When to Emit What O11y Signal?</title>
      <link>https://akshayd-dev.pages.dev/posts/when-to-emit-what-o11y-signal/</link>
      <pubDate>Thu, 04 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/when-to-emit-what-o11y-signal/</guid>
      <description>&lt;p&gt;The intention of this page is to put together the &lt;em&gt;Observability Signal Guidelines&lt;/em&gt; which will provide the required visibility into the systems without hurting the cost aspect of the solution.&lt;/p&gt;
&lt;p&gt;Three basic observability signals that any application emits are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Metrics,&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Traces and&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Logs&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The general question is - &lt;em&gt;&lt;strong&gt;When to emit what signal?&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The answer lies in the &lt;em&gt;intent&lt;/em&gt; behind the signal being emitted. &lt;em&gt;&lt;strong&gt;What do you intend to measure with the Observability signal that you are emitting?&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enhancing Observability with OTel Custom Processors</title>
      <link>https://akshayd-dev.pages.dev/posts/enhancing-observability-with-otel-custom-processors/</link>
      <pubDate>Sun, 27 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/enhancing-observability-with-otel-custom-processors/</guid>
      <description>&lt;p&gt;Observability is crucial for modern distributed systems, enabling engineers to monitor, debug, and optimize their applications effectively. OpenTelemetry (Otel) has emerged as a comprehensive, vendor-neutral observability framework for collecting, processing, and exporting telemetry data such as traces, metrics, and logs.&lt;/p&gt;
&lt;p&gt;This blog post will explore how custom processors in OpenTelemetry can significantly enhance your observability strategy, making it highly customizable and powerful.&lt;/p&gt;
&lt;p&gt;The repo link where I have implemented a very simple Otel-Custom-Processor.&lt;br&gt;
&lt;a href=&#34;https://github.com/AkshayD110/otel-custom-processor/tree/master&#34;&gt;https://github.com/AkshayD110/otel-custom-processor/tree/master&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
