Skip to content

Commit

Permalink
fix wrong naming in How does gRPC work? section (ByteByteGoHq#28)
Browse files Browse the repository at this point in the history
  • Loading branch information
umutbozdag authored Oct 22, 2023
1 parent 3daa772 commit 542d4c1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ The diagram below illustrates the overall data flow for **gRPC**.

Step 1: A REST call is made from the client. The request body is usually in JSON format.

Steps 2 - 4: The order service (gRPC client) receives the REST call, transforms it, and makes an RPC call to the payment service. gPRC encodes the **client stub** into a binary format and sends it to the low-level transport layer.
Steps 2 - 4: The order service (gRPC client) receives the REST call, transforms it, and makes an RPC call to the payment service. gRPC encodes the **client stub** into a binary format and sends it to the low-level transport layer.

Step 5: gRPC sends the packets over the network via HTTP2. Because of binary encoding and network optimizations, gRPC is said to be 5X faster than JSON.

Expand Down

0 comments on commit 542d4c1

Please sign in to comment.