News for hackers. Stuff that matters.
Re:gRPC vs. REST: Understand gRPC, OpenAPI and REST and When... by pphysch on Wednesday January 22, 2025 @08:21PM (#42799537)
How could gRPC be simpler without sacrificing performance?
Re:gRPC vs. REST: Understand gRPC, OpenAPI and REST and When... by jeeyoungk on Wednesday January 22, 2025 @08:28PM (#42799593)
There's two parts to gRPC's performance

- 1. multiplexing protocol implemented on top of HTTP/2 - 2. serialization format via protobuf

For most companies, neither 1 or 2 is needed, but the side effect of 2 (of having structured schema) is good enough. This was the idea behind twrip - https://github.com/twitchtv/twirp - not sure whether this is still actively used / maintained, but it's protobuf as json over HTTP.

Re:gRPC vs. REST: Understand gRPC, OpenAPI and REST and When... by liontwist on Wednesday January 22, 2025 @08:25PM (#42799566)
What kind of performance? Read? Write? Bandwidth?
Re:gRPC vs. REST: Understand gRPC, OpenAPI and REST and When... by dlahoda on Wednesday January 22, 2025 @08:27PM (#42799583)
grpc "urls" and data are binary.

binary with schema separation.

3x smaller payload.