Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Draw a General Purpose Diagram #705

Merged
merged 1 commit into from
Mar 5, 2024
Merged

Draw a General Purpose Diagram #705

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,24 @@ bazel test //... `
This causes Bazel to run the commands through an all-in-one `CAS`, `scheduler`
and `worker`.

## How it Works

This diagram is a high-level overview of the data flow in the NativeLink system. It refers to NativeLink concepts like Scheduler pool, Worker pool, and CAS rather than the cloud concepts like functions, compute nodes, and object storage to which they correspond.

```mermaid
sequenceDiagram
participant build server (client)
participant scheduler pool
participant worker pool
participant cas
build server (client)->>scheduler pool: queue jobs
scheduler pool->>worker pool: route jobs
worker pool->>cas: upload artifacts
worker pool->>scheduler pool: result download instructions
scheduler pool->>build server (client): result download instructions
cas->>build server (client): service queries
build server (client)->>cas: service queries
```
## ❄️ Installing with Nix

**Installation requirements:**
Expand Down
Loading