Protocol Buffer Services: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 37: | Line 37: | ||
{{Internal|GRPC_Concepts#gRPC_and_Protocol_Buffer_Services|gRPC and Protocol Buffer Services}} | {{Internal|GRPC_Concepts#gRPC_and_Protocol_Buffer_Services|gRPC and Protocol Buffer Services}} | ||
=Example= | =Example= |
Revision as of 01:56, 11 May 2024
External
Internal
Overview
Protocol Buffers can define services that use messages to exchange data.
A service is a set of endpoints, introduced by the rpc
keyword, with different semantics that can be used to call into the service, by sending a request, and then receiving a response.
service SomeService {
rpc SomeEndpoint(SomeRequest) returns (SomeResponse);
rpc SomeOtherEndpoint(SomeOtherRequest) returns (SomeOtherResponse);
}
message SomeRequest {
...
}
message SomeResponse {
...
}
message SomeOtherRequest {
...
}
message SomeOtherResponse {
...
}
This is how you define an API.
The service and the client code is generated by a framework, and the preferred one is gRPC.