GitBook: [main] 58 pages and 9 assets modified
boneyard93501
gitbook-bot
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 41 KiB |
BIN
.gitbook/assets/image (10).png
Normal file
|
After Width: | Height: | Size: 55 KiB |
BIN
.gitbook/assets/image (11).png
Normal file
|
After Width: | Height: | Size: 71 KiB |
BIN
.gitbook/assets/image (9).png
Normal file
|
After Width: | Height: | Size: 54 KiB |
@ -1,7 +1,5 @@
|
||||
# Concepts
|
||||
|
||||
|
||||
|
||||
The Fluence solution enables a new class of decentralized Web3 solutions providing technical, security and business benefits otherwise not available. In order for solution architects and developers to realize these benefits, a shift in philosophy and implementation is required. With the Fluence tool chain available, developers should find it possible to code meaningful Web3 solutions in short order once an understanding of the core concepts and Aqua is in place.
|
||||
|
||||
The remainder of this section introduces the core concepts underlying the Fluence solution.
|
||||
@ -112,5 +110,3 @@ Figure 8: Stylized Par Execution
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
4
p2p.md
@ -8,13 +8,13 @@ In some network models, such as client server, the request-response model genera
|
||||
|
||||
Figure 2: Client Server Request Response Model
|
||||
|
||||
|
||||
|
||||
|
||||
The Fluence peer-to-peer protocol, on the other hand, allows for a much more effective Request-Response processing pattern where responses are forward-chained to the next consuming service\(s\) without having to make the return trip to the client. See Figure 3.
|
||||
|
||||
Figure 3: Fluence P2P Protocol Request Response Model
|
||||
|
||||
|
||||
|
||||
|
||||
In a Fluence p2p implementation, our client application would call a credit check API deployed or proxy-ed on some peer and then send the response directly to the SMS API service possibly deployed on another peer -- similar to the flow depicted in Figure 1.
|
||||
|
||||
|
||||
@ -1,7 +1,5 @@
|
||||
# Quick Start
|
||||
|
||||
|
||||
|
||||
The Fluence solution enables a new class of decentralized Web3 solutions providing technical, security and business benefits otherwise not available. In order for solution architects and developers to realize these benefits, a shift in philosophy and implementation is required. With the Fluence tool chain available, developers should find it possible to code meaningful Web3 solutions in short order once an understanding of the core concepts and Aqua is in place.
|
||||
|
||||
The remainder of this section introduces the core concepts underlying the Fluence solution.
|
||||
@ -112,5 +110,3 @@ Figure 8: Stylized Par Execution
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||