Re:The Idempotency-Key HTTP header field
by vettyvignesh on Sunday July 04, 2021 @04:27PM
(#27732351)
Pardon my ignorance but why does it matter that you're using RPC/graphQL or REST based service, isn't the underlying protocol still HTTP? So this spec would still be applicable, right?
[ Parent
| on HN ]
Re:The Idempotency-Key HTTP header field
by denysvitali on Sunday July 04, 2021 @04:38PM
(#27732427)
AFAIK, in Google's case the end application doesn't really see the "GRPC HTTP headers" but instead they convert an incoming HTTP request to one of their frontends and route it to multiple backends (sending effectively the HTTP body serialized via GRPC), and then the frontends will simply re-create the response by unifying them.
Not a Googler, this is what I understood from reading similar things over multiple posts. Feel free to correct me.
Re:The Idempotency-Key HTTP header field
by mcqueenjordan on Sunday July 04, 2021 @05:05PM
(#27732613)
The underlying protocol is not necessarily HTTP.
Re:The Idempotency-Key HTTP header field
by staticassertion on Sunday July 04, 2021 @06:19PM
(#27733091)
I think it is necessarily HTTP/2, but would be happy to learn I'm mistaken - it's not something I'm overly confident about.
https://developers.googleblog.com/2015/02/introducing-grpc-n...
gRPC uses HTTP/2.0 yes, so headers are a concept, but imagine taking it one step further, for instance using WebSockets. There is no concept of headers within an individual WebSocket message, so it would need to be encapsulated in an application-specific way anyway.