<?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>DEV Community: Obaidullah Siddiqui</title>
    <description>The latest articles on DEV Community by Obaidullah Siddiqui (@obaid786).</description>
    <link>https://dev.to/obaid786</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253998%2F5f1852bb-113f-49cd-8d39-51c921a26cd9.jpg</url>
      <title>DEV Community: Obaidullah Siddiqui</title>
      <link>https://dev.to/obaid786</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/obaid786"/>
    <language>en</language>
    <item>
      <title>EMOTIONAL Assistant</title>
      <dc:creator>Obaidullah Siddiqui</dc:creator>
      <pubDate>Thu, 19 Nov 2026 14:30:21 +0000</pubDate>
      <link>https://dev.to/obaid786/emotional-assistant-62p</link>
      <guid>https://dev.to/obaid786/emotional-assistant-62p</guid>
      <description>&lt;p&gt;Launching v2 of my Emotion-Aware Chatbot: A lesson in backend deployment hell&lt;/p&gt;

&lt;p&gt;I recently rebuilt and deployed version 2 of my AI chatbot, a system that uses LangGraph, FastAPI, and React to classify user intent, route queries to different agents, and perform Retrieval-Augmented Generation (RAG) with guardrails.&lt;/p&gt;

&lt;p&gt;While building the features was intellectually stimulating, getting the backend to run live in the real world was an entirely different beast. I spent days fighting with deployment platforms. I tried Fly.io, but hit roadblocks with their persistent volume dashboards and 5-minute trial limits that kept suspending my machines. I tried Hugging Face Spaces, only to find out they had recently paywalled Docker deployments. I tried Koyeb, but their free tier no longer supports the persistent storage my SQLite and FAISS databases required.&lt;/p&gt;

&lt;p&gt;I finally settled on Render. While it required adapting my Dockerfile to handle dynamic port binding, and forcing fresh Vercel builds to capture new environment variables, it finally worked.&lt;/p&gt;

&lt;p&gt;For anyone deploying a full-stack AI app: the code is only 50 percent of the battle. Understanding platform limitations, memory constraints, and environment variables is the other 50 percent.&lt;/p&gt;

&lt;p&gt;Frontend: emotinal-chat-frontend.vercel.app&lt;br&gt;
Backend:&lt;a href="https://emotional-logical-chatbot-2zrz.onrender.com/api/health" rel="noopener noreferrer"&gt;https://emotional-logical-chatbot-2zrz.onrender.com/api/health&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
