You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In microservices scenario, in addition to directly accessing services through domain names or k8s svc, they are usually called base on the third-party registration center.
In grpc-go, the appropriate way is to implement a self-defined resolver, the resovler monitor the node updates in the registration center and update the connections.
However, there seems to be no official implementation currently provided. Developers can only develop independently. Can we provide a official plugin library, and the library includes some extension implementations such as resolvers supporting third-party registry? In this way, it improves the convenience for developers to use like me
The text was updated successfully, but these errors were encountered:
The team does not have the time or expertise to implement an official resolver for the use-case that you are asking. But if you want to implement it, please send us a detailed proposal. We can have a discussion and then move towards an implementation.
In microservices scenario, in addition to directly accessing services through domain names or k8s svc, they are usually called base on the third-party registration center.
In grpc-go, the appropriate way is to implement a self-defined resolver, the resovler monitor the node updates in the registration center and update the connections.
However, there seems to be no official implementation currently provided. Developers can only develop independently. Can we provide a official plugin library, and the library includes some extension implementations such as resolvers supporting third-party registry? In this way, it improves the convenience for developers to use like me
The text was updated successfully, but these errors were encountered: