Architecture Layers

Step-by-Step Flow: 1. Users interact through the Explorer, Kaisar Cloud Portal, or Worker Portal, depending on their role and requirements. -> Explorer is a public site, for viewing the summaries, reports of Network Capacity. Kaisar Cloud Portal is for End User (GPU Consumer). and Worker Portal is for (GPU Provider).

2. All incoming connections pass through the VPN and Firewall for secure access. The IAM system verifies user credentials and permissions.

3. Requests are routed to the API Gateway, which is running in a cluster mode to ensure high availability and load balancing.

4.The API Gateway uses a round-robin rule to distribute incoming requests to instances of the Backend( Service Management, Worker Management, Billing, Monitoring & Alert, Logging, and Analytics modules). Each of these modules runs multiple instances to handle the load efficiently.

5. Depending on the request type, it's processed by the relevant backend service. For instance, compute jobs might be directed to the GPU Cluster through Worker Management.

6. Some operations, those requiring immutable records or enhanced security, interact with the PEAQ Blockchain.

7. After processing, responses are sent back through the API Gateway to the respective frontend interface, providing users with the needed information. -> For asynchronous requests, the Portal will connect to a WebSocket endpoint on the API Gateway. Once the process is completed, the result will be returned to the Portal through WebSocket events.

Below is the detailed working of the Kaisar Network, organized into architecture layers: