<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Soumya Ranjan Nanda</title>
    <description>The latest articles on Forem by Soumya Ranjan Nanda (@soumya_ranjannanda_168b9).</description>
    <link>https://forem.com/soumya_ranjannanda_168b9</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3871120%2F35f212dd-1482-4665-8246-430c06ed9bfd.png</url>
      <title>Forem: Soumya Ranjan Nanda</title>
      <link>https://forem.com/soumya_ranjannanda_168b9</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/soumya_ranjannanda_168b9"/>
    <language>en</language>
    <item>
      <title>Why AI Features Fail in Production Even When The Demo Works</title>
      <dc:creator>Soumya Ranjan Nanda</dc:creator>
      <pubDate>Wed, 15 Apr 2026 19:44:58 +0000</pubDate>
      <link>https://forem.com/soumya_ranjannanda_168b9/why-ai-features-fail-in-production-even-when-the-demo-works-5b54</link>
      <guid>https://forem.com/soumya_ranjannanda_168b9/why-ai-features-fail-in-production-even-when-the-demo-works-5b54</guid>
      <description>&lt;p&gt;The demo is usually the easy part.&lt;/p&gt;

&lt;p&gt;Production is where the real engineering starts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;latency budgets&lt;/li&gt;
&lt;li&gt;degraded modes&lt;/li&gt;
&lt;li&gt;validation&lt;/li&gt;
&lt;li&gt;observability&lt;/li&gt;
&lt;li&gt;trust boundaries&lt;/li&gt;
&lt;li&gt;retrieval quality&lt;/li&gt;
&lt;li&gt;cost control&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I wrote a practical breakdown from a software engineering angle here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/p/3929c4263952" rel="noopener noreferrer"&gt;https://medium.com/p/3929c4263952&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Curious which failure mode teams underestimate most.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
      <category>systemdesign</category>
      <category>llm</category>
    </item>
    <item>
      <title>The debugging story behind PrematureCloseException in a high-volume bulk workflow</title>
      <dc:creator>Soumya Ranjan Nanda</dc:creator>
      <pubDate>Wed, 15 Apr 2026 06:30:05 +0000</pubDate>
      <link>https://forem.com/soumya_ranjannanda_168b9/the-debugging-story-behind-prematurecloseexception-in-a-high-volume-bulk-workflow-4k44</link>
      <guid>https://forem.com/soumya_ranjannanda_168b9/the-debugging-story-behind-prematurecloseexception-in-a-high-volume-bulk-workflow-4k44</guid>
      <description>&lt;p&gt;When more concurrency broke my bulk workflow&lt;/p&gt;

&lt;p&gt;I increased concurrency to speed up a high-volume bulk workflow.&lt;/p&gt;

&lt;p&gt;At first, it looked like the right move. Smaller runs got faster, throughput improved, and the pipeline seemed healthier.&lt;/p&gt;

&lt;p&gt;Then larger runs started failing with &lt;code&gt;PrematureCloseException&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;That was the moment I realized the problem was no longer just performance. It had become a &lt;strong&gt;system pressure&lt;/strong&gt; problem.&lt;/p&gt;

&lt;p&gt;A few lessons from the debugging journey:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;more parallelism does &lt;strong&gt;not&lt;/strong&gt; always mean more throughput&lt;/li&gt;
&lt;li&gt;chunk size is not just a batch setting — it becomes a stability boundary&lt;/li&gt;
&lt;li&gt;retries only help after the concurrency model is sane&lt;/li&gt;
&lt;li&gt;connection pool behavior matters a lot more under load&lt;/li&gt;
&lt;li&gt;partial-failure handling makes bulk workflows much more trustworthy&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What finally helped was not one magic fix. It was a combination of:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;reducing unsafe parallelism&lt;/li&gt;
&lt;li&gt;tuning chunk size more carefully&lt;/li&gt;
&lt;li&gt;adding retry with backoff&lt;/li&gt;
&lt;li&gt;stabilizing connection pool behavior&lt;/li&gt;
&lt;li&gt;treating concurrency as a budget instead of a goal&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I wrote the full debugging story here:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://medium.com/p/758f87e312d5&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Curious how others handle this kind of issue in bulk or async workflows.&lt;/p&gt;

</description>
      <category>springboot</category>
      <category>java</category>
      <category>distributedsystems</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>How I Scaled Bulk Search in Spring Boot with Parallel Batch Jobs and Controlled Concurrency</title>
      <dc:creator>Soumya Ranjan Nanda</dc:creator>
      <pubDate>Mon, 13 Apr 2026 10:57:38 +0000</pubDate>
      <link>https://forem.com/soumya_ranjannanda_168b9/how-i-scaled-bulk-search-in-spring-boot-with-parallel-batch-jobs-and-controlled-concurrency-21j</link>
      <guid>https://forem.com/soumya_ranjannanda_168b9/how-i-scaled-bulk-search-in-spring-boot-with-parallel-batch-jobs-and-controlled-concurrency-21j</guid>
      <description>&lt;p&gt;I recently wrote about a backend problem that looked simple at first but became a real architecture and reliability challenge under load:&lt;/p&gt;

&lt;p&gt;scaling bulk search in Spring Boot with parallel batch jobs and controlled concurrency&lt;/p&gt;

&lt;p&gt;A few lessons stood out for me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;parallelism helps, but only until it starts hurting upstream systems&lt;/li&gt;
&lt;li&gt;chunking is not just a batch setting, it becomes a stability boundary&lt;/li&gt;
&lt;li&gt;partial failure handling matters as much as throughput&lt;/li&gt;
&lt;li&gt;caching repeated enrichment work can remove a surprising amount of unnecessary load&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One of the biggest shifts for me was moving away from a more limited blocking flow into parallel batch jobs while still keeping pressure on downstream systems under control.&lt;/p&gt;

&lt;p&gt;I wrote the full breakdown here:&lt;br&gt;
&lt;a href="https://medium.com/p/6a742ad7af9d" rel="noopener noreferrer"&gt;https://medium.com/p/6a742ad7af9d&lt;/a&gt;&lt;/p&gt;

</description>
      <category>java</category>
      <category>distributedsystems</category>
      <category>systemdesign</category>
      <category>architecture</category>
    </item>
    <item>
      <title>What I learned building bulk search for large datasets in React + Spring Boot</title>
      <dc:creator>Soumya Ranjan Nanda</dc:creator>
      <pubDate>Mon, 13 Apr 2026 05:43:30 +0000</pubDate>
      <link>https://forem.com/soumya_ranjannanda_168b9/what-i-learned-building-bulk-search-for-large-datasets-in-react-spring-boot-4id1</link>
      <guid>https://forem.com/soumya_ranjannanda_168b9/what-i-learned-building-bulk-search-for-large-datasets-in-react-spring-boot-4id1</guid>
      <description>&lt;p&gt;Bulk search sounds easy until real users start pasting spreadsheet data, uploading messy CSVs, and expecting clear results for thousands of records.&lt;/p&gt;

&lt;p&gt;I recently built a bulk search workflow in React + Spring Boot, and this article is a practical breakdown of what actually mattered: normalization, validation, chunking, frontend performance, and partial-failure reporting.&lt;/p&gt;

&lt;p&gt;Read the full article here: &lt;a href="https://medium.com/p/ea69f155054a" rel="noopener noreferrer"&gt;https://medium.com/p/ea69f155054a&lt;/a&gt;&lt;/p&gt;

</description>
      <category>react</category>
      <category>aws</category>
      <category>java</category>
      <category>springboot</category>
    </item>
  </channel>
</rss>
