Table of Contents

Server-side Application

The Server-side Application model is the recommended starting point for new RecroGrid Framework applications.

From a deployment perspective, it consists of two applications: a browser-facing Blazor host application and a separate backend API application. During development, the Blazor application has a host/server part and an interactive Client part. The host manages OpenID Connect sign-in, SessionAuth, and API proxying, while the backend API owns the main RecroGrid Framework server runtime, business logic, Entity Framework integration, and data access.

The backend API is the server-side foundation of the solution, so the complete setup workflow begins by creating and configuring it before the Blazor application.

See Application Models for the deployment, development, and request-flow comparison between the supported models.

For a complete client-side reference with every host and Client setting in one place, see Server-side Application configuration.

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, and those parts are deployed together.

The backend API is a required part of the modern Server-side Application solution. It provides the server-side RecroGrid Framework runtime and data-access foundation consumed through the Blazor host.

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.
  • 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 inside the backend application layer.
  • 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 form one coherent client-server solution.

Development-time solution shape

A typical solution contains the following projects and responsibilities:

Solution
├── Application.Api
│   ├── RecroGrid Framework server runtime
│   ├── Business logic
│   ├── Entity Framework
│   └── Database access
├── Application
│   ├── Blazor host
│   ├── OpenID Connect
│   ├── SessionAuth endpoints
│   └── API proxy
└── Application.Client
    ├── Interactive Blazor UI
    ├── Routes
    └── RecroGrid Framework client integration

The setup workflow follows the dependency direction of this architecture: backend API, database and API authentication first, followed by the Blazor host and interactive client.

Workflow

flowchart TD
    api[Create Backend API]
    database[Configure Database and Entity Framework]
    apiAuth[Configure Backend API Authentication]
    blazor[Create Blazor Application]
    sessionAuth[Configure SessionAuth]
    proxy[Configure API Proxy]
    client[Configure Client]
    run[Run and Initialize Complete Solution]

    api --> database --> apiAuth --> blazor --> sessionAuth --> proxy --> client --> run

Next step