Skip to content
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

A ugly design #4673

Open
MegaByte875 opened this issue Feb 28, 2025 · 2 comments
Open

A ugly design #4673

MegaByte875 opened this issue Feb 28, 2025 · 2 comments

Comments

@MegaByte875
Copy link

Image

If an RPC service endpoint is not started, the calling service will crash, wouldn't this couple them together? In a production environment, if service A depends on services B and C, and at some point, service B or C fails and becomes unreachable for a period of time, should service A also detect this and exit?

@kevwan
Copy link
Contributor

kevwan commented Feb 28, 2025

It depends on your logic, this is fail-fast strategy.

But still you can set NonBlock: true to change the behavior.

BTW: this is by design, and I don't think it's a ugly design.

@zhqqqy
Copy link

zhqqqy commented Mar 6, 2025

or add an exponential backoff retry mechanism?

It depends on your logic, this is fail-fast strategy.

But still you can set NonBlock: true to change the behavior.

BTW: this is by design, and I don't think it's a ugly design.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants