Table of Contents

Blazor WebAssembly Application Architecture

This model has two deployment units: a standalone browser-hosted Blazor WebAssembly client application and a separate backend API application. The client communicates directly with the API without an ASP.NET Core Blazor host acting as an authentication or API proxy.

flowchart TD
    client[Browser / Blazor WebAssembly client application]
    api[Backend API application]
    db[(Database)]

    client --> api
    api --> db

Responsibilities

  • Browser and Blazor WebAssembly client host the interactive user interface and obtain authentication credentials from the configured identity provider.
  • Authentication layer issues bearer tokens to the client according to the selected OIDC setup.
  • Direct API access sends HTTP requests from the browser to the RecroGrid Framework API without a host-side proxy.
  • 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 its persistence integration.
  • Database stores the business data and RecroGrid Framework metadata needed by the application.

Because the browser talks directly to the API, this model requires aligned API base-address configuration, bearer-token support, and CORS configuration on the API side.

Next step