| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – Rate Limit</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/</link><description>Recent content in Rate Limit 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/limit/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs3-V2: Dubbo Go's built-in current limit usage tutorial</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/internally/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/internally/</guid><description/></item><item><title>Docs3-V2: Current Limiting Tutorial Based on Sentinel</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/sentinel/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/sentinel/</guid><description/></item><item><title>Docs3-V2: Polaris-Based Current Limiting Tutorial</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/polaris/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/polaris/</guid><description/></item><item><title>Docs3-V2: Set current limit for the server</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/tps_limiter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/tps_limiter/</guid><description> |
| <h2 id="1-preparations">1. Preparations</h2> |
| <ul> |
| <li>dubbo-go cli tools and dependent tools have been installed</li> |
| <li>Create a new demo application</li> |
| </ul> |
| <h2 id="2-modify-the-current-limiting-logic-and-verify">2. Modify the current limiting logic and verify</h2> |
| <p>Dubbo-go provides users with built-in flow-limiting rejection logic, and supports users to define the required flow-limiting mechanism and rejection logic according to their own business scenarios.</p> |
| <p>Under normal circumstances, no flow limit is set. When the user configures the flow limit logic and parameters on the server side, it will</p> |
| <h3 id="21-configure-current-limiting-parameters">2.1 Configure current limiting parameters</h3> |
| <p>go-server/conf/dubbogo.yaml: Configure current limiting parameters</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">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>: <span style="color:#2aa198">&#34;&#34;</span> <span style="color:#586e75"># read from pb</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">tps.limiter</span>: <span style="color:#2aa198">&#34;method-service&#34;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">tps.limit.strategy</span>: <span style="color:#2aa198">&#34;slidingWindow&#34;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">tps.limit.rejected.handler</span>: <span style="color:#2aa198">&#34;default&#34;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">tps.limit.interval</span>: <span style="color:#2aa198">1000</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">tps.limit.rate</span>: <span style="color:#2aa198">3</span> |
| </span></span></code></pre></div><p>Parameter Description:</p> |
| <ul> |
| <li>tps.limiter: current limiter selection. method-service is a current limiter built into the framework, which can configure service and method-level current limit logic, which can be customized.</li> |
| <li>tps.limit.strategy: selection of current limiting strategy, slidingWindow is a built-in current limiting strategy of the framework, which can reject requests exceeding the traffic limit in the window in the form of a sliding window.</li> |
| <li>tps.limit.rejected.handler: rejection strategy, default is the default rejection method, returns an empty object, can be customized</li> |
| <li>tps.limit.interval: current limit window interval, the unit is ms.</li> |
| <li>tps.limit.rate: The traffic limit in the window, the unit is the number of requests.</li> |
| </ul> |
| <p>According to the above configuration, the server only allows the current interface to be called three times within one second.</p> |
| <h3 id="22-initiate-a-super-flow-request-to-verify-the-current-limiting-capability">2.2 Initiate a super-flow request to verify the current-limiting capability</h3> |
| <p>Set the client&rsquo;s request logic to request five times per second, and calculate the success rate.</p> |
| <p>go-client/cmd/client.go</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> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">func</span> <span style="color:#268bd2">main</span>() { |
| </span></span><span style="display:flex;"><span>config. <span style="color:#268bd2">SetConsumerService</span>(grpcGreeterImpl) |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">if</span> err <span style="color:#719e07">:=</span> config.<span style="color:#268bd2">Load</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>logger.<span style="color:#268bd2">Info</span>(<span style="color:#2aa198">&#34;start to test dubbo&#34;</span>) |
| </span></span><span style="display:flex;"><span>req <span style="color:#719e07">:=</span> <span style="color:#719e07">&amp;</span>api.HelloRequest{ |
| </span></span><span style="display:flex;"><span>Name: <span style="color:#2aa198">&#34;Laurence&#34;</span>, |
| </span></span><span style="display:flex;"><span>} |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">for</span> { |
| </span></span><span style="display:flex;"><span>goodCount <span style="color:#719e07">:=</span> <span style="color:#2aa198">0</span> |
| </span></span><span style="display:flex;"><span>badCount <span style="color:#719e07">:=</span> <span style="color:#2aa198">0</span> |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">for</span> { |
| </span></span><span style="display:flex;"><span>time.<span style="color:#268bd2">Sleep</span>(time.Millisecond<span style="color:#719e07">*</span><span style="color:#2aa198">200</span>) |
| </span></span><span style="display:flex;"><span>reply, _ <span style="color:#719e07">:=</span> grpcGreeterImpl.<span style="color:#268bd2">SayHello</span>(context.<span style="color:#268bd2">Background</span>(), req) |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">if</span> reply.Name <span style="color:#719e07">==</span> <span style="color:#2aa198">&#34;&#34;</span> { |
| </span></span><span style="display:flex;"><span>badCount<span style="color:#719e07">++</span> |
| </span></span><span style="display:flex;"><span>} <span style="color:#719e07">else</span> { |
| </span></span><span style="display:flex;"><span>goodCount<span style="color:#719e07">++</span> |
| </span></span><span style="display:flex;"><span>} |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">if</span> badCount <span style="color:#719e07">+</span> goodCount <span style="color:#719e07">==</span> <span style="color:#2aa198">5</span>{ |
| </span></span><span style="display:flex;"><span><span style="color:#719e07">break</span> |
| </span></span><span style="display:flex;"><span>} |
| </span></span><span style="display:flex;"><span>} |
| </span></span><span style="display:flex;"><span>logger.<span style="color:#268bd2">Infof</span>(<span style="color:#2aa198">&#34;Success rate = %v\n&#34;</span>, <span style="color:#b58900">float64</span>(goodCount)<span style="color:#719e07">/</span><span style="color:#b58900">float64</span>(goodCount <span style="color:#719e07">+</span> badCount)) |
| </span></span><span style="display:flex;"><span>} |
| </span></span><span style="display:flex;"><span>} |
| </span></span></code></pre></div><p>It can be seen in the log that the request success rate is 0.6, and only three requests are allowed to be executed per second.</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-bash" data-lang="bash"><span style="display:flex;"><span>INFO cmd/client.go:62 Success <span style="color:#268bd2">rate</span> <span style="color:#719e07">=</span> 0.6 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>INFO cmd/client.go:62 Success <span style="color:#268bd2">rate</span> <span style="color:#719e07">=</span> 0.6 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>INFO cmd/client.go:62 Success <span style="color:#268bd2">rate</span> <span style="color:#719e07">=</span> 0.6 |
| </span></span></code></pre></div><p>You can see the rejection information in the server log:</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-bash" data-lang="bash"><span style="display:flex;"><span>ERROR tps/filter.go:84 The invocation was rejected due to over the limiter limitation... |
| </span></span></code></pre></div></description></item><item><title>Docs3-V2: dubbogo 3.0 flexible service</title><link>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/adaptive-service/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/golang-sdk/tutorial/governance/limit/adaptive-service/</guid><description> |
| <h1 id="flexible-load-balancing-flexible-service">Flexible load balancing (flexible service)</h1> |
| <p>Flexible service is a decentralized intelligent load balancing component, and it is also one of the major new features in Dubbo-go version 3.0. Flexible services are still in the early experimental stage, and this feature will continue to be optimized in subsequent versions, and we will work with the Dubbo community to explore a set of best practices suitable for microservice scenarios.</p> |
| <p>The traditional load balancing algorithm is implemented by algorithms such as random nodes and RoundRobin. Their limitation is that they do not know the load situation of the current service provider, and the algorithm always calls different service providers with as fair a probability as possible. In practice, fairness does not mean high performance, and cluster service performance is also related to multiple factors such as service load and task complexity. In order to solve the shortcomings of traditional load balancing algorithms, Dubbo-go introduced flexible services in version 3.0, realizing dynamic capacity evaluation and distribution functions.</p> |
| <p>Capacity assessment is the core of flexible services, which can dynamically assess the capacity level of the server. In the process of capacity evaluation, the two core indicators are TPS and response time. It is necessary to balance the relationship between system utilization and system performance, so that the whole is in the best state.</p> |
| <ul> |
| <li>TPS reflects system utilization from the perspective of service providers. Before the system pressure is saturated, the greater the number of requests, the higher the system utilization rate. However, if the request volume is further increased until the system is oversaturated, the problem of overload occurs, resulting in a downward trend in overall efficiency.</li> |
| <li>Response time reflects system performance from the perspective of service callers. Before the system pressure is not saturated, the response time increases linearly with the number of requests, but when the amount of requests is further increased until the system is oversaturated, the response time and the number of requests increase exponentially.</li> |
| </ul> |
| <p><img src="https://dubbo.apache.org/imgs/docs3-v2/golang-sdk/samples/adaptive-service/adaptive.png" alt="img"></p> |
| <p>Flexible services are collected during the call</p> |
| <p>In Dubbo-go version 3.0, service flexible load balancing is supported. In the microservice scenario, the client will collect the hardware resource consumption of the downstream server instance of the service during the invocation process, and select the most suitable downstream instance for invocation through capacity evaluation and screening strategies, thereby improving the overall system performance.</p> |
| <p>Service flexibility will continue to be optimized in subsequent iterations, seeking to explore best practices with the Dubbo community.</p></description></item></channel></rss> |
