design-docs/Dominator: add GrpcAndRest design document#261
Open
Vikramarjuna wants to merge 1 commit into
Open
Conversation
Adds a design document describing how gRPC and REST will be added alongside the existing SRPC protocol, sharing the same TLS endpoint, client certificates and authorisation logic. Topics covered: protocol routing on a shared port, reuse of the existing certificate-based access control, three-level rate limiting to compensate for HTTP/2 multiplexing, schema generation from the existing Go message structs, type converters between internal Go structs and the generated pb/ types, error handling, metrics with a protocol dimension, and an incremental per-API migration strategy.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a design document describing how gRPC and REST will be added alongside the existing SRPC protocol, sharing the same TLS endpoint, client certificates and authorisation logic.
Topics covered: protocol routing on a shared port, reuse of the existing certificate-based access control, three-level rate limiting to compensate for HTTP/2 multiplexing, schema generation from the existing Go message structs, type converters between internal Go structs and the generated pb/ types, error handling, metrics with a protocol dimension, and an incremental per-API migration strategy.