2 ms·
REST is not very structured and means something a little different to every implementer. Systems like Thrift and GRPC build an uambiguous contract around the re
by closeparen 8y ago
REST is not very structured and means something a little different to every implementer. Systems like Thrift and GRPC build an uambiguous contract around the request and response schema, with IDL serving as documentation whose correctness is mechanically enforced. Since both parties have the IDL, the messages can be packed efficiently on the wire without any field names and in formats that are less computationally intensive to parse/serialize than JSON. It’s also relatively clear which IDL changes are breaking and which are backwards compatible (the latter being the only kind you can sanely make in a running distributed system). The wire protocol can be less chatty and better suited to multiplexing a high volume of traffic along the same socket, which was a shortcoming of HTTP until relatively recently with HTTP2.
- vram22 8y agoThanks, makes sense.