Use mDNS to support zero-configuration for apollo client?

[nobodyiam]

Apollo client relies on the meta server to locate the config service addresses, which requires the user to configure the meta server address properly.

It's not a very complex configuration, but it does increase some burden and it's easy to make mistakes as different environments have different meta server addresses.
However, with the concept of Multicast DNS(mDNS), it's possible to achieve the zero-configuration goal: the apollo client simply uses http://apollo.local to access apollo meta server and it requires no configuration, e.g. no need to configure the DNS server for this domain and users don't need to configure the meta server address when using apollo-client.

[Anilople]

Sounds great!

[nisiyong]

If there are several config-services, I think the client could not recognize the right environment one.

[nobodyiam]

This is a potential issue. Each environment should have a distinct LAN, or the mDNS request would be sent to apollo-configservices in multiple environments.

[qmwu2000]

It works well for strictly managed environments, such as production or QA environment, in a low priority. For development environment in the office or even in local dev box, Apollo root configure address should/could be overridden by existing methods.

…

On May 7, 2022, at 08:17, Jason Song ***@***.*** ***@***.***>> wrote: This is a potential issue. Each environment should have a distinct LAN, or the mDNS request would be sent to apollo-configservices in multiple environments. — Reply to this email directly, view it on GitHub <#4338 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASQE75Y7BUNX2GE45OH6U3VIWZAPANCNFSM5VGV27GA>. You are receiving this because you are subscribed to this thread.

[nobodyiam]

Right, we could keep using the current meta address locate logic and fallback to mDNS if no address could be found.