Ecology Overview
Nacos ecology documents explain how Nacos works with application frameworks, cloud-native infrastructure, migration and sync tools, monitoring systems, and AI toolchains.
If you only want to understand Nacos core capabilities, start with Overview, Configuration Overview, Service Discovery Overview, and AI Registry Overview. Ecology documents are more useful after you know which integration scenario you need.
Choose by scenario
| Scenario | Read |
|---|---|
| Java microservice integration | Nacos With Dubbo, Spring, Spring Boot, Spring Cloud |
| Cloud-native infrastructure | CoreDNS, Istio |
| Kubernetes service sync | Kubernetes service discovery sync, Nacos Controller service sync |
| Registry migration and sync | NacosSync User Manual |
| Prometheus application target discovery | Use Nacos For Prometheus Service Discovery |
| AI toolchain integration | Nacos MCP Router |
Relationship with core capabilities
Ecology capabilities usually build around Nacos core capabilities:
- Application frameworks use Nacos mainly for configuration management and service discovery.
- Kubernetes, CoreDNS, and Istio integrations use service discovery or sync service discovery information to other systems.
- NacosSync is used for registry migration and multi-registry sync.
- Prometheus service discovery lets Prometheus obtain business application targets from Nacos.
- AI ecosystem components such as MCP Router focus on tool invocation and service discovery for AI applications.
These documents involve external projects, framework versions, and deployment environments. Before using them, also read the official documents of the external projects and verify version compatibility in a test environment.
Ecology capability status
The Ecology section includes long-standing integration documents and ecosystem capabilities that are still evolving. Some Kubernetes-related sync and controller capabilities may change their APIs, configuration, and maintenance model. When using them, also read Experimental Features Overview.