epistemophiliac/fabric-samples
1
0
Fork 0
mirror of https://github.com/hyperledger/fabric-samples.git synced 2026-06-17 07:25:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typo (#1048)

Browse source 
Signed-off-by: Pushp Vashisht <pushptyagi1@gmail.com>
This commit is contained in:
Pushp Vashisht 2023-06-20 10:47:16 +05:30 committed by GitHub
parent 2c0fe75438
commit bc3a6bfa05
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
full-stack-asset-transfer-guide/docs/ApplicationDev/01-FabricGateway.md
View file

@ -62,7 +62,7 @@ Notice that the client only needs to interact directly with the Gateway peer. Th
For security, client applications should connect only to Gateway peers within their own organization or, if the client's organization does not host their own peers, to Gateway peers of a trusted organization.
The following diagram demonstrates recommended practice for enabling access to an organization cluster through a single endpoint address while maintaining high availability. This use of a load balancer or ingress controller as a proxy in front of a set of internal endpoints is commonly used when deploying Web or Application servers, so this pattern is well established. The gRPC communication between client and Gateway atually uses HTTP/2 as its transport.
The following diagram demonstrates recommended practice for enabling access to an organization cluster through a single endpoint address while maintaining high availability. This use of a load balancer or ingress controller as a proxy in front of a set of internal endpoints is commonly used when deploying Web or Application servers, so this pattern is well established. The gRPC communication between client and Gateway actually uses HTTP/2 as its transport.
![Fabric Gateway deployment](../images/ApplicationDev/fabric-gateway-deployment.png)