Skip to main content

Nacos Plugin

The Nacos module is implemented as a control-plane plugin that can provide naming, discovery, and config-center behavior inside one runtime.

Runtime Facts​

ItemValue
Go modulegithub.com/go-lynx/lynx-nacos
Config prefixlynx.nacos
Runtime plugin namenacos.control.plane
Public API shapeplugin-manager lookup plus methods such as GetConfig(...), GetConfigSources(), GetNamespace()

What The Implementation Provides​

The code supports:

  • optional naming client
  • optional config client
  • service registration and discovery
  • config loading from dataId and group
  • config watchers
  • retry, metrics, and circuit breaker helpers

That is why Nacos belongs in the control-plane category, not in a narrow "config only" or "registry only" category.

Configuration​

lynx:
  nacos:
    server_addresses: "127.0.0.1:8848"
    namespace: "public"
    enable_register: true
    enable_discovery: true
    enable_config: true
    service_config:
      service_name: "my-service"
      group: "DEFAULT_GROUP"
      cluster: "DEFAULT"

What The Official Template Uses​

The official template does not enable Nacos by default. The current scaffold uses Polaris as its control-plane example instead.

That means:

  • Nacos is supported, but not the default governance backend shown by lynx-layout
  • you add it when your environment already standardizes on Nacos for naming, config, or both
  • this page should be read as a concrete replacement or extension path, not as the current template's built-in control plane

How To Consume It​

plugin := lynx.Lynx().GetPluginManager().GetPlugin("nacos.control.plane")
nacosPlugin := plugin.(*nacos.PlugNacos)

sources, err := nacosPlugin.GetConfigSources()
source, err := nacosPlugin.GetConfig("app.yaml", "DEFAULT_GROUP")

The old import examples using github.com/go-lynx/lynx/plugin/nacos are outdated for the current repository layout.