Skip to content

Commit ad209d3

Browse files
authored
Update architecture.md
1 parent c70ccd6 commit ad209d3

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

docs/architecture.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,29 @@ To address the need to support a distributed network, we plan to take several ac
77
3. Automatic/Manual source picking strategy
88
4. Agnostic core, with the ability to run integrate with any GraphQL client
99

10+
#### Standalone mode
11+
12+
```mermaid
13+
graph LR;
14+
c[Browser/Node]-->|executes|g[Graph-Client];
15+
g-->op[Orchestrator/Query Planner]
16+
op-->sA[Subgraph A];
17+
op-->sB[Subgraph B];
18+
```
19+
20+
21+
#### With any GraphQL client
22+
1023
```mermaid
1124
graph LR;
1225
c[Any GraphQL Client]-->|fetch/Urql Exchange/Apollo Link|l[Compatibility Layer];
13-
l-->|executes|g[GraphQL Schema/Executor];
14-
g-->op[Orchestrator]
26+
l-->|executes|g[Graph-Client];
27+
g-->op[Orchestrator/Query Planner]
1528
op-->sA[Subgraph A];
1629
op-->sB[Subgraph B];
1730
```
1831

32+
1933
### Subgraph Composition
2034

2135
To allow simple and efficient client-side composition, we'll use [`graphql-tools`](https://www.graphql-tools.com/) to create a remote schema / Executor, then can be hooked into the GraphQL client.

0 commit comments

Comments
 (0)