You can run Demo Provider and Demo Consumer only, the default discovery strategy is Multicast by configuration center broadcast, do not run the two parts on the same machine, if you have to do so, set
multicast://184.108.40.206:1234?unicast=false, or the unicast send to consumer will be taken by provider, and the same for consumers. Only multicast has this issue
You can run multiple Demo Provider and Demo consumer to verify load balance. Demo Consumer can run multi instance directly. Because of port conflict, you can either run multi Demo Providers on different machines or modify the value of
conf/dubbo.properties under the install directory of
You can add Simple Monitor as a monitor center, the default discovery strategy is Multicast by configuration center broadcast, display the dependency relationship, call times and cost
You can use Zookeeper instead of Multicast as the configuration center, after Zookeeper Registry installation, modify
conf/dubbo.properties under the installation directory of Demo Provider, Demo Consumer and Simple Monitor, change the value of
redis://127.0.0.1:6379 for Redis Registry). the value for Simple Registry is
Zookeeper configuration address is recommended
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.