[Enhancement] Use Nacos NamingService to save meta data

[karsonto]

Search before asking

• [X] I had searched in the issues and found no similar issues.

Enhancement Request

When using Nacos as a meta service should use naming service to save meta data.

Describe the solution you'd like

When using nacos as meta storage, it uses configService to save client info currently:

But I think this usage is inappropriate, because when nacos uses a cluster, config data will be persisted to the database, TPS is very low, and these service-related information should be saved to the metadata of the registration center

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct *

[xwm1992]

As far as I know, nacos name service has no way to persist the meta data to be stored, why do you want to use name service instead of config service?

[karsonto]

I have found that subscriber information is stored on meta storage, which is frequently updated and not suitable for persistent storage.

[xwm1992]

I have found that subscriber information is stored on meta storage, which is frequently updated and not suitable for persistent storage.

But if you use name service, if one eventmesh goes down, how can you ensure that the subscription information on this eventmesh is loaded to other meshes?

[karsonto]

You can consider using a permanent instance to save the mata data when registering, and the information should not be lost when the server goes down.