I stopped treating Flask as a full-stack renderer and started separating frontend/backend like a real production system

I recently completed a video streaming project, and one of the biggest things I learned had nothing to do with UI design or APIs…

It was architecture.

Usually, when I build with Flask or FastAPI, I render the frontend directly from the backend.

This time, I decided to split everything:

• React frontend
• Separate backend API
• Independent deployments

At first it felt unnecessary.

But during the project, I started understanding why modern apps are structured this way.

A few things I learned:

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

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

• media optimization
• uploads
• storage
• transformations
• performance tradeoffs

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

Sometimes the biggest upgrade isn’t learning a new framework.

It’s changing how you structure your systems.