Use gRPC outbound by default for internal traffic #4492
Merged
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.
What changed?
Cadence server will use gRPC outbound for internal traffic by default.
User can still opt-out by setting dynamic config
system.enableGRPCOutbound
tofalse
.However we should consider TChannel for internal communication deprecated and will work towards removing it in the future.
Why?
Another step in gRPC migration. We have been running gRPC internally for the last few months, it looks stable to be used by default.
How did you test it?
Potential risks
Release notes
Updated changelog.
Documentation Changes