Table of Contents

Server-side Application Architecture

The recommended server-side model has two deployment units: a browser-facing Blazor host application and a separate backend API application. The Blazor application has a host/server part and an interactive client part during development, but those parts are deployed together.

flowchart TD
    browser[Browser]
    host[Blazor host application]
    api[Backend API application]
    db[(Database)]

    browser --> host
    host --> api
    api --> db

Responsibilities

  • Browser and interactive client render the application UI and issue requests to the host origin.
  • Blazor host/server part owns the application origin, OpenID Connect sign-in, authenticated session, and proxy endpoints.
  • Blazor interactive client part provides the UI layer, route structure, and RecroGrid Framework client integration.
  • SessionAuth keeps the client aligned with the authenticated host session and controls route-aware reauthentication behavior.
  • API proxy forwards downstream API requests from the host to the separate backend API application instead of exposing direct browser bearer-token calls.
  • Backend API application hosts the RecroGrid Framework server runtime, most business logic, entity operations, and framework services.
  • Entity Framework manages the application data model and database integration.
  • Database stores the operational business data and RecroGrid Framework metadata required by the application.

This architecture is designed for professional business applications where integrated authentication, centralized API access, and maintainable host-side control are more important than keeping the browser as an isolated API consumer.

Next step