forked from docs/doc-exports
zhoumeng
3275979377
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: zhoumeng <zhoumeng35@huawei.com> Co-committed-by: zhoumeng <zhoumeng35@huawei.com>
32 lines
7.0 KiB
HTML
32 lines
7.0 KiB
HTML
<a name="elb_pro_0005"></a><a name="elb_pro_0005"></a>
|
|
|
|
<h1 class="topictitle1">Product Advantages</h1>
|
|
<div id="body18191719"><div class="section" id="elb_pro_0005__section106161345824"><h4 class="sectiontitle">Advantages of Dedicated Load Balancers</h4><ul id="elb_pro_0005__ul4438681418511"><li id="elb_pro_0005__li61386558161449">Robust performance<p id="elb_pro_0005__p6263149193913"><a name="elb_pro_0005__li61386558161449"></a><a name="li61386558161449"></a>Each load balancer has exclusive use of isolated resources, meeting your requirements for handling a massive number of requests. A single load balancer deployed in one AZ can handle up to 20 million concurrent connections.</p>
|
|
<p id="elb_pro_0005__p41704924161458">If you deploy a load balancer in multiple AZs, its performance such as the number of new connections and the number of concurrent connections will multiply. For example, if you deploy a dedicated load balancer in two AZs, it can handle up to 40 million concurrent connections.</p>
|
|
<div class="note" id="elb_pro_0005__note1439316386124"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="elb_pro_0005__ul923217451122"><li id="elb_pro_0005__li17232345111210">If requests are from the Internet, the load balancer in each AZ you select routes the requests based on source IP addresses. If you deploy a load balancer in two AZs, the requests the load balancers can handle will be doubled.</li><li id="elb_pro_0005__li0765191117216">For requests from a private network:<ul id="elb_pro_0005__ul187611211172118"><li id="elb_pro_0005__li13767152811815">If clients are in an AZ you have selected when you created the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer becomes unavailable, requests are distributed by the load balancer in another AZ you have selected.<p id="elb_pro_0005__p93011631387"><a name="elb_pro_0005__li13767152811815"></a><a name="li13767152811815"></a>If the load balancer is available but the connections that the load balancer needs to handle exceed the amount defined in the specifications, service may be interrupted. To address this issue, you need upgrade specifications. </p>
|
|
</li><li id="elb_pro_0005__li18762161119217">If clients are in an AZ that is not selected when you created the load balancer, requests are distributed by the load balancer in each AZ you select based on source IP addresses.</li></ul>
|
|
</li><li id="elb_pro_0005__li147061182517">If clients are in a VPC that is different from where the load balancer works, the load balancer in the AZ where the original VPC subnet resides routes the requests. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ.</li></ul>
|
|
</div></div>
|
|
</li><li id="elb_pro_0005__li910139118614">High availability<p id="elb_pro_0005__p1480365618614"><a name="elb_pro_0005__li910139118614"></a><a name="li910139118614"></a>ELB can route traffic uninterruptedly. If your servers in one AZ are unhealthy, it automatically routes traffic to healthy servers in other AZs. ELB provides a comprehensive health check system to ensure that incoming traffic is routed only to healthy backend servers, improving the availability of your applications.</p>
|
|
</li><li id="elb_pro_0005__li6423824716">Ultra-high security<p id="elb_pro_0005__p16773129816"><a name="elb_pro_0005__li6423824716"></a><a name="li6423824716"></a>ELB supports TLS 1.3 and can route HTTPS requests to backend servers. You can select security policies or customize security policies that fit your security requirements.</p>
|
|
</li><li id="elb_pro_0005__li248013404119">Multiple protocols<p id="elb_pro_0005__p92691543417"><a name="elb_pro_0005__li248013404119"></a><a name="li248013404119"></a>ELB supports Quick UDP Internet Connection (QUIC), TCP, UDP, HTTP, and HTTPS, so that they can route requests to different types of applications.</p>
|
|
</li><li id="elb_pro_0005__li157315516113">High flexibility<p id="elb_pro_0005__p1568653513"><a name="elb_pro_0005__li157315516113"></a><a name="li157315516113"></a>ELB can route requests based on their content, such as the request method, header, URL, path, and source IP address. They can also redirect requests to another listener or URL, or return a fixed response to the clients.</p>
|
|
</li><li id="elb_pro_0005__li108770162710">No limits<p id="elb_pro_0005__p987204271"><a name="elb_pro_0005__li108770162710"></a><a name="li108770162710"></a>ELB can route requests to both servers on the cloud and on premises, allowing you to leverage cloud resources to handle burst traffic.</p>
|
|
</li><li id="elb_pro_0005__li3657268018631">Ease-of-use<p id="elb_pro_0005__p6071866818631"><a name="elb_pro_0005__li3657268018631"></a><a name="li3657268018631"></a>ELB provides a diverse set of algorithms that allow you to configure different traffic routing policies to meet your requirements while keeping deployments simple.</p>
|
|
</li></ul>
|
|
</div>
|
|
<div class="section" id="elb_pro_0005__section956154410326"><h4 class="sectiontitle">Advantages of <span id="elb_pro_0005__ph1356164414328">Shared</span> Load Balancers</h4><ul id="elb_pro_0005__ul13561449326"><li id="elb_pro_0005__li9567443327">High availability<p id="elb_pro_0005__p756544163210"><a name="elb_pro_0005__li9567443327"></a><a name="li9567443327"></a><span id="elb_pro_0005__ph17252846245">Shared</span> load balancers can route traffic across AZs, ensuring that your services are uninterrupted. If servers in an AZ are unhealthy, ELB automatically routes traffic to healthy servers in other AZs. <span id="elb_pro_0005__ph126614207246">Shared</span> load balancers provide a comprehensive health check mechanism to ensure that incoming traffic is routed to only healthy backend servers, improving the availability of your applications.</p>
|
|
<div class="fignone" id="elb_pro_0005__fig20561944123219"><span class="figcap"><b>Figure 1 </b>High availability</span><br><span><img class="vsd" id="elb_pro_0005__image756204417322" src="en-us_image_0000001794660657.png"></span></div>
|
|
</li><li id="elb_pro_0005__li356114417328">Multiple protocols<p id="elb_pro_0005__p185674414323"><a name="elb_pro_0005__li356114417328"></a><a name="li356114417328"></a>ELB supports TCP, UDP, HTTP, and HTTPS protocols to route requests to different types of applications.</p>
|
|
</li><li id="elb_pro_0005__li135694417324">Ease-of-use<p id="elb_pro_0005__p1656104453217"><a name="elb_pro_0005__li135694417324"></a><a name="li135694417324"></a><span id="elb_pro_0005__ph10613303257">Shared</span> load balancers provide a diverse set of algorithms that allow you to configure different traffic routing policies to meet your requirements while keeping deployments simple.</p>
|
|
</li><li id="elb_pro_0005__li85612449326">High reliability<p id="elb_pro_0005__p1456194433215"><a name="elb_pro_0005__li85612449326"></a><a name="li85612449326"></a>Shared load balancers are deployed in two AZs by default and can distribute traffic more evenly.</p>
|
|
</li></ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="elb_pro_0000.html">Service Overview</a></div>
|
|
</div>
|
|
</div>
|
|
|