commit | 5ea48734c81f3f4969001ebf28c6c73443c8d1e9 | [log] [tgz] |
---|---|---|
author | Zhen Ju <juzhen@huawei.com> | Sat Sep 29 11:31:06 2018 +0800 |
committer | Zhen Ju <juzhen@huawei.com> | Sat Sep 29 11:31:06 2018 +0800 |
tree | 0d5a209c6cbb68c24b02d02ef2efe371700080f0 | |
parent | ed864bd9d56e8d1cc2a7f482dc6a4c62295d8f64 [diff] |
Update the istio related dependencies. Since istio specifies both revision 2137d91963 and tag v0.6.0 for envoyproxy/go-control-plane, while the code changes between the revision and tag will cause incompatibility. So replace go-control-plane's tag with the revision in repalce block.
A service mesh implementation based on go chassis.
One big advantage of Mesher is it is able to work with go-chassis in same service mesh control plane like Istio. Without Istio they can work together with ServiceComb Service center and running on any infrastructure(docker, VM, baremetal). So if you choose go as your programing language, you can use go-chassis to gain better performance, and you can freely use other programing language which suit your service the most
Mesher support both linux and windows OS, that makes possible that .Net service can work with java, go, python service in one distributed system easily
Refer to mesher-examples
Install ServiceComb service-center
build and run, use go mod(go 1.11+, experimental but a recommended way)
cd mesher GO111MODULE=on go mod download #optional GO111MODULE=on go mod vendor go build mesher.go ./mesher