3 ms·
It's a little hard for me to understand what if anything this presents. At first I thought perhaps Protocol Buffers didn't have an RPC layer, and that this was
by rektide 12y ago
It's a little hard for me to understand what if anything this presents. At first I thought perhaps Protocol Buffers didn't have an RPC layer, and that this was bringing Protocol Buffers up to a comparable level of competitors like Thrift. Checking the Protocol Buffers docs though, I see they do already have services.
Is this simply a consistent, cross-language looking interface for authoring/consuming Protocol Buffers services? What makes this different from other Protocol Buffer implementations?
- a11r 12y agoProtocol Buffers didn't really have an RPC engine - the services feature was limited to generating some interfaces. gRPC provides an actual RPC engine with required network functionality.
- haberman 12y agoJust to add to a11r's comment: - this is not a new Protocol Buffer implementation. It uses the existing Protocol Buffers implementation for serialization/deserialization. - this is actual implementation for the service declarations you could write in .proto files already (previously Protocol Buffers could only generate interface stubs, without implementation).