<?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: Oghosa Divine Osaigbovo</title>
    <description>The latest articles on DEV Community by Oghosa Divine Osaigbovo (@devine-byte).</description>
    <link>https://dev.to/devine-byte</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%2F3922004%2F1c04e2ea-167e-4377-a5f5-73da73346e08.jpg</url>
      <title>DEV Community: Oghosa Divine Osaigbovo</title>
      <link>https://dev.to/devine-byte</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/devine-byte"/>
    <language>en</language>
    <item>
      <title>I stopped treating Flask as a full-stack renderer and started separating frontend/backend like a real production system</title>
      <dc:creator>Oghosa Divine Osaigbovo</dc:creator>
      <pubDate>Sat, 16 May 2026 07:55:23 +0000</pubDate>
      <link>https://dev.to/devine-byte/i-stopped-treating-flask-as-a-full-stack-renderer-and-started-separating-frontendbackend-like-a-17fl</link>
      <guid>https://dev.to/devine-byte/i-stopped-treating-flask-as-a-full-stack-renderer-and-started-separating-frontendbackend-like-a-17fl</guid>
      <description>&lt;p&gt;I recently completed a video streaming project, and one of the biggest things I learned had nothing to do with UI design or APIs…&lt;/p&gt;

&lt;p&gt;It was architecture.&lt;/p&gt;

&lt;p&gt;Usually, when I build with Flask or FastAPI, I render the frontend directly from the backend.&lt;/p&gt;

&lt;p&gt;This time, I decided to split everything:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React frontend&lt;/li&gt;
&lt;li&gt;Separate backend API&lt;/li&gt;
&lt;li&gt;Independent deployments&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;At first it felt unnecessary.&lt;/p&gt;

&lt;p&gt;But during the project, I started understanding &lt;em&gt;why&lt;/em&gt; modern apps are structured this way.&lt;/p&gt;

&lt;p&gt;A few things I learned:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Frontend and backend scale differently&lt;/li&gt;
&lt;li&gt;Deployment becomes more flexible&lt;/li&gt;
&lt;li&gt;Working with third-party services is cleaner&lt;/li&gt;
&lt;li&gt;React feels much more powerful when it’s fully independent&lt;/li&gt;
&lt;li&gt;API design matters a LOT more when the frontend is detached&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I also worked heavily with Cloudinary for video handling/streaming, and that taught me a lot about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;media optimization&lt;/li&gt;
&lt;li&gt;uploads&lt;/li&gt;
&lt;li&gt;storage&lt;/li&gt;
&lt;li&gt;transformations&lt;/li&gt;
&lt;li&gt;performance tradeoffs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It wasn’t a perfect project, but I came out understanding frontend/backend separation way better than before.&lt;/p&gt;

&lt;p&gt;Sometimes the biggest upgrade isn’t learning a new framework.&lt;/p&gt;

&lt;p&gt;It’s changing how you structure your systems.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>architecture</category>
      <category>api</category>
    </item>
  </channel>
</rss>
