Separate Development, Co-Hosted Deployment

Overview

The frontend and backend run in the same process (or the same container), with requests routed by URL prefix or route priority. Each side iterates independently during development and ships as a single artifact for deployment.

When to Use

• The project needs a frontend UI but you don't want to maintain two deployment pipelines
• Solo or small-team project where you want to simplify operations
• You already have a backend API and need to add frontend pages under the same domain (avoiding CORS)
• You need SSR for the first paint or a skeleton screen, then let the client-side SPA take over

Core Architecture Pattern

Browser Request
    │
    ▼