-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Connect instead of gRPC #155
Conversation
331b27e
to
865106e
Compare
e1d3c1d
to
93ad391
Compare
Ran |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please update the README section on service architecture to reflect the change from grpc-gateway -> connect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrote out a few comments but realized I was more reviewing and asking questions about the connect API and not your actual code lol. Looks great!
add code generation using `protoc-gen-connect-go` replace gRPC server code w/ equivalnt Connect code replace grpc-gateway w/ Vanguard
replace gRPC client usage in the CLI with Connect client remove gRPC code generation updated README.md to reflect the switch to Connect
also updated bufbuild/httplb to v0.3.0
aac14e1
to
c43e27f
Compare
This PR swaps gRPC for Connect in both the server and CLI implementations. For compatibility with running instances of the Perseus service, we enable the gRPC wire protocol for the client. We have also replaced
grpc-gateway
with Vanguard (connectrpc.com/vanguard) for JSON/REST support in the server's API.I have done compatibility testing using an old (gRPC) client hitting a new (Connect) server, a new client hitting an old server, and a new client hitting a new server.
The generated metrics are slightly different due to differences between the gRPC and Connect runtimes, but the things being monitored are the same.