OnyeOne Request Flow

The following document describes the overall architectural workflow of OnyeOne's platform, focusing on how requests are routed and processed based on specific headers and provider configurations.

Overview

OnyeOne's platform is designed to handle API requests dynamically based on the x-backend-id and x-api-key headers provided in each request. The architecture allows providers to either:

Use a custom backend they maintain.

Leverage the platform's managed backend.

Workflow Diagram

Below is a high-level description of how requests are handled:

Key Benefits of the Architecture

Flexibility: Allows providers to bring their own backends or use the managed backend.

Scalability: Efficiently routes requests to appropriate backends without bottlenecks.

Security: Ensures only authorized API users can access resources using x-api-key validation.

Overview

Workflow Diagram

Key Benefits of the Architecture

Example Scenarios

Scenario 1: Request with `x-backend-id`

Scenario 2: Request without `x-backend-id`

Scenario 3: Invalid API Key

OnyeOne Request Flow

Overview#

Workflow Diagram#

Key Benefits of the Architecture#

Example Scenarios#

Scenario 1: Request with x-backend-id#

Scenario 2: Request without x-backend-id#

Scenario 3: Invalid API Key#

Overview

Workflow Diagram

Key Benefits of the Architecture

Example Scenarios

Scenario 1: Request with `x-backend-id`

Scenario 2: Request without `x-backend-id`

Scenario 3: Invalid API Key