fluencelabs/examples
1
0
Fork 0
mirror of https://github.com/fluencelabs/examples synced 2025-06-12 01:21:20 +00:00
Code Issues Projects Releases Wiki Activity

replace figure 1 code with jpeg

Browse Source
This commit is contained in:
boneyard93501
2021-10-21 09:23:03 -05:00
parent 73b7a544af
commit 12230c9ccc
3 changed files with 19 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
aqua-examples/ceramic-demo/README.md
View File

@ -6,24 +6,7 @@
In order to use services available outside the Fluence network, such as [IPFS](https://ipfs.io/) or [Ceramic](https://ceramic.network/), we need to create adapters, which are generally implemented with Wasm modules, that allow us to bridge the Fluence network with many other networks and protocols. Once our adapter services are in place, we can use Aqua to seamlessly integrate such resources into our distributed, peer-to-peer application composition.
```mermaid
sequenceDiagram
title: Figure 1: Stylized Use of Adapters
participant C as Fluence Client Peer
participant F as Relay Node
participant S as Peer(s) hosting adapter(s)
participant O as Exogenous API/Runtime
C ->> F: Launch Aqua script to compose adapter services + other services
F ->> S: Call adapter service(s)
S ->> S: Call host binary
S ->> O: Request to exogenous resource
O ->> S: Response from exogenous service(s)
S ->> S: Update Aqua workflow (Particle)
S ->> F: Return result
F ->> C: Return result
```
![image](assets/figure_1.jpg)
In this example, we develop an adapter for the Ceramic [CLI API](https://developers.ceramic.network/build/cli/api/) with the goal of seamlessly integrating Ceramic services into Fluence peer-to-peer applications composed with Aqua. See Figure 1.

BIN
aqua-examples/ceramic-demo/assets/figure_1.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 124 KiB

18
aqua-examples/ceramic-demo/assets/figure_1_code.md Normal file
View File

@ -0,0 +1,18 @@
```mermaid
sequenceDiagram
title: Figure 1: Stylized Use of Adapters
participant C as Fluence Client Peer
participant F as Relay Node
participant S as Peer(s) hosting adapter(s)
participant O as Exogenous API/Runtime
C ->> F: Launch Aqua script to compose adapter services + other services
F ->> S: Call adapter service(s)
S ->> S: Call host binary
S ->> O: Request to exogenous resource
O ->> S: Response from exogenous service(s)
S ->> S: Update Aqua workflow (Particle)
S ->> F: Return result
F ->> C: Return result
```