commit | 6130e36a7c8b5ad4a7a6100d55c73055728ab8e3 | [log] [tgz] |
---|---|---|
author | min <z82507200@gmail.com> | Thu Aug 01 14:45:01 2019 +0800 |
committer | GitHub <noreply@github.com> | Thu Aug 01 14:45:01 2019 +0800 |
tree | 87b90e7c65966e926bef974719c0941b3708ee09 | |
parent | fb6af3cbd393439568df739eb59b056dbd9feabb [diff] | |
parent | 67d9b4f18d47e4b321576917b720bd78d8a928fe [diff] |
Merge pull request #12 from qixiaobo/refactor-code-style code-style-refactor
Dubbo Proxy, a gateway of Dubbo, switch from HTTP request to Dubbo protocol,then invoke Dubbo service and return to the result. Later Dubbo Proxy would combine several features, including circuit breaker, current-limiting, api management.
HTTP request format:
{application Name}/{Interface name}?version={version}&group={group}
Group and version is the mapping data in Dubbo service.
http POST body:
{ "methodName" : "sayHello", "paramTypes" : ["org.apache.dubbo.demo.model.User"], "paramValues": [ { "id": 23, "username": "testUser" } ] }
application.yml
proxy.registry.address: zookeeper://127.0.0.1:2181 #registry center address, same as Dubbo service's proxy.metadata-report.address: zookeeper://127.0.0.1:2181 #metadata center address, used by paramType search, support for dubbo 2.7 or later