| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – Traffic Management</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/traffic/</link><description>Recent content in Traffic Management on Apache Dubbo</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/traffic/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs3-V2: routing rules</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/traffic/mesh_router/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/traffic/mesh_router/</guid><description> |
| <h2 id="introduction-to-routing-rules">Introduction to routing rules</h2> |
| <p><a href="https://www.yuque.com/docs/share/c132d5db-0dcb-487f-8833-7c7732964bd4?#">&ldquo;Microservice Mesh Routing Scheme Draft V2&rdquo;</a></p> |
| <h2 id="introduction">Introduction</h2> |
| <p>Routing rules, in simple terms, are to send <strong>specific request</strong> traffic to <strong>specific service provider</strong> according to <strong>specific conditions</strong>. Thereby realizing the distribution of flow.</p> |
| <p>In the definition of Dubbo3 unified routing rules, two resources in yaml format need to be provided: virtual service and destination rule. Its format is very similar to the routing rules defined by service mesh.</p> |
| <ul> |
| <li>virtual service</li> |
| </ul> |
| <p>Define the host, which is used to establish a relationship with the destination rule. <br> |
| Define service matching rules<br> |
| Define match matching rules<br> |
| After matching a specific request, search and verify the target cluster, and use the fallback mechanism for empty cases.</p> |
| <p>-destination rule</p> |
| <p>Define a specific cluster subset and the tags that the subset is adapted to. The tags are obtained from the url exposed on the provider side and try to match.</p> |
| <h2 id="provide-capabilities">Provide capabilities</h2> |
| <h3 id="routing-configuration-based-on-configuration-center">Routing configuration based on configuration center</h3> |
| <p>For the sample example, see <a href="https://github.com/apache/dubbo-go-samples/tree/master/route/meshroute">Mesh Router</a></p> |
| <h4 id="1-routing-rule-file-annotation">1. Routing rule file annotation</h4> |
| <p>The routing rules are only for the client. For the server, you only need to label specific parameters when the service is provided.</p> |
| <h5 id="11-virtual-service">1.1 virtual-service</h5> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#268bd2">apiVersion</span>: service.dubbo.apache.org/v1alpha1 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">kind</span>: VirtualService |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">metadata</span>: {<span style="color:#268bd2">name</span>: demo-route} |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">spec</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75"># Use a regular expression to match the service name, only a request that satisfies the service name can be routed.</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75"># For this example, if the request does not satisfy the service name, the provider will not be found directly</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75"># - services:</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75"># - { regex: org.apache.dubbo.UserProvider* }</span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">route detail</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75"># Matching rules, if (sourceLabel) client url satisfies the parameter `trafficLabel: xxx`, the match can be successful</span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">sourceLabels</span>: {<span style="color:#268bd2">trafficLabel</span>: xxx} |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: xxx-project |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: <span style="color:#586e75"># Once the above match rule is matched, the subset named isolation defined in dest_rule will be selected</span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">destination</span>: {<span style="color:#268bd2">host: demo, subset</span>: isolation} |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">sourceLabels</span>: {<span style="color:#268bd2">trafficLabel</span>: testing-trunk} |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: testing-trunk |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: <span style="color:#586e75"># Once the above match rule is matched, the subset named testing-trunk defined in dest_rule will be selected</span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">destination</span>: {<span style="color:#268bd2">host: demo, subset</span>: testing-trunk} |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: testing <span style="color:#586e75"># There is no match, the bottom-up logic, if the above-mentioned dissatisfaction is met, it will be matched.</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">destination</span>: {<span style="color:#268bd2">host: demo, subset</span>: testing} |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">services</span>: |
| </span></span><span style="display:flex;"><span> - {<span style="color:#268bd2">exact</span>: com.apache.dubbo.sample.basic.IGreeter} |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">hosts</span>: [demo] <span style="color:#586e75"># Match the host in dest_rule.yml as demo</span> |
| </span></span></code></pre></div><h5 id="12-destination-rule">1.2 destination-rule</h5> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#268bd2">apiVersion</span>: service.dubbo.apache.org/v1alpha1 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">kind</span>: DestinationRule |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">metadata</span>: { <span style="color:#268bd2">name</span>: demo-route } |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">spec</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subsets</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">labels</span>: { <span style="color:#268bd2">env-sign: xxx, tag1</span>: hello } |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: isolation |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">labels</span>: { <span style="color:#268bd2">env-sign</span>: yyy } |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: testing-trunk |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">labels</span>: { <span style="color:#268bd2">env-sign</span>: zzz } |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: testing |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">trafficPolicy</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">loadBalancer</span>: { <span style="color:#268bd2">simple</span>: ROUND_ROBIN } |
| </span></span></code></pre></div><h4 id="2-client-and-server-routing-parameter-settings">2. Client and server routing parameter settings</h4> |
| <ul> |
| <li> |
| <p>client side</p> |
| <p>dubbogo.yml</p> |
| <p>Define configuration center</p> |
| </li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span> <span style="color:#268bd2">config-center</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">protocol</span>: zookeeper |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: <span style="color:#2aa198">127.0.0.1</span>:<span style="color:#2aa198">2181</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">data-id</span>: <span style="color:#2aa198">&#34;dubbo-go-samples-configcenter-zookeeper-client&#34;</span> |
| </span></span></code></pre></div><p>Publish the configuration to the configuration center through the API in the code, or manually configure it in advance.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-go" data-lang="go"><span style="display:flex;"><span>dynamicConfiguration, err <span style="color:#719e07">:=</span> config.<span style="color:#268bd2">GetRootConfig</span>().ConfigCenter.<span style="color:#268bd2">GetDynamicConfiguration</span>() |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">if</span> err <span style="color:#719e07">!=</span> <span style="color:#cb4b16">nil</span> { |
| </span></span><span style="display:flex;"><span> <span style="color:#b58900">panic</span>(err) |
| </span></span><span style="display:flex;"><span>} |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">// publish mesh route config |
| </span></span></span><span style="display:flex;"><span><span style="color:#586e75"></span>err = dynamicConfiguration. <span style="color:#268bd2">PublishConfig</span>(<span style="color:#2aa198">&#34;dubbo.io. MESHAPPRULE&#34;</span>, <span style="color:#2aa198">&#34;dubbo&#34;</span>, MeshRouteConf) |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">if</span> err <span style="color:#719e07">!=</span> <span style="color:#cb4b16">nil</span> { |
| </span></span><span style="display:flex;"><span> <span style="color:#719e07">return</span> |
| </span></span><span style="display:flex;"><span>} |
| </span></span></code></pre></div><p>server side</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">registries</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">demoZK</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">protocol</span>: zookeeper |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">timeout</span>: 3s |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">address</span>: <span style="color:#2aa198">127.0.0.1</span>:<span style="color:#2aa198">2181</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">protocols</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">triple</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: tri |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">port</span>: <span style="color:#2aa198">20000</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">provider</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">services</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">GreeterProvider</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">interface</span>: com.apache.dubbo.sample.basic.IGreeter <span style="color:#586e75"># must be compatible with grpc or dubbo-java</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">params</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">env-sign</span>: zzz <span style="color:#586e75"># server label, corresponding to the testing in the destination Rule, that is, the bottom-up logic</span> |
| </span></span></code></pre></div><h4 id="3-run-method">3. Run method</h4> |
| <p>Run this example directly using goland</p> |
| <p>After running, it can be observed that all client traffic is routed to the server. According to the source label, there is no virtualService hit, so it is routed to the bottom-up test.</p></description></item><item><title>Docs3-V2: Elegant online and offline</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/traffic/graceful_shutdown/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/traffic/graceful_shutdown/</guid><description> |
| <h1 id="gracefully-log-in-and-out">Gracefully log in and out</h1> |
| <h2 id="introduction">Introduction</h2> |
| <p>In the process of stable production, container scheduling is completely controlled by k8s, and microservice governance is completely maintained and managed by service framework or operation and maintenance personnel. In the case of releasing a new version or expanding or shrinking the capacity, the old container instance will be terminated and replaced with a new container instance. For an online production environment carrying high traffic, if the connection of this replacement process is unreasonable, the A large number of wrong requests are caused in a short period of time, triggering alarms and even affecting normal business. For larger manufacturers, the loss caused by problems in the release process will be huge.</p> |
| <p>Therefore, the appeal of graceful online and offline is put forward. This requires that the service framework, on the basis of having stable service invocation capabilities and traditional service governance capabilities, should provide stable guarantees during the process of going online and offline, thereby reducing operation and maintenance costs and improving application stability.</p> |
| <h2 id="expected-effect">Expected effect</h2> |
| <p>Ideally, the effect of graceful offline and offline is that in a distributed system carrying a large amount of traffic, all component instances can be expanded, reduced, and rolled over at will. In this case, it is necessary to ensure stable tps and rt, to ensure that no request errors are caused by the application going offline.</p> |
| <h2 id="how-to-use">How to use</h2> |
| <p>The Dubbo-go app enables graceful log-off and offline by default.</p> |
| <p>Related reading: <a href="https://developer.aliyun.com/article/860775">[Design and Practice of Dubbo-go Elegant Online and Offline]</a></p></description></item></channel></rss> |
