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>
26 lines
3.2 KiB
HTML
26 lines
3.2 KiB
HTML
<a name="elb_pro_0006"></a><a name="elb_pro_0006"></a>
|
|
|
|
<h1 class="topictitle1">Application Scenarios</h1>
|
|
<div id="body1516093773361"><div class="section" id="elb_pro_0006__section747414212515"><h4 class="sectiontitle">Heavy-Traffic Applications</h4><p id="elb_pro_0006__p1344111419235">For an application with heavy traffic, such as a large portal or mobile app store, ELB evenly distributes incoming traffic to multiple backend servers, balancing the load while ensuring steady performance.</p>
|
|
<p id="elb_pro_0006__p27855038171257">Sticky sessions ensure that requests from one client are always forwarded to the same backend server for fast processing.</p>
|
|
<div class="fignone" id="elb_pro_0006__fig145320429220"><span class="figcap"><b>Figure 1 </b>Session stickiness</span><br><span><img class="vsd" id="elb_pro_0006__image7238166114817" src="en-us_image_0000001747739756.png"></span></div>
|
|
</div>
|
|
<div class="section" id="elb_pro_0006__section1151610117243"><h4 class="sectiontitle">Applications with Predictable Peaks and Troughs in Traffic</h4><p id="elb_pro_0006__p5408524171345">For an application that has predictable peaks and troughs in traffic volumes, ELB works with Auto Scaling to add or remove backend servers to keep up with changing demands. An example is flash sales, during which application traffic spikes in a short period. ELB can work with Auto Scaling to run only the required number of backend servers to handle the load of your application.</p>
|
|
<div class="fignone" id="elb_pro_0006__fig1927134415176"><span class="figcap"><b>Figure 2 </b>Flexible scalability</span><br><span><img class="vsd" id="elb_pro_0006__image533212444485" src="en-us_image_0000001747380872.png"></span></div>
|
|
</div>
|
|
<div class="section" id="elb_pro_0006__section430324872511"><h4 class="sectiontitle">Zero SPOFs</h4><p id="elb_pro_0006__p66668867171438">ELB routinely performs health checks on backend servers to monitor their health. If any backend server is detected unhealthy, ELB will not route requests to this server until it recovers.</p>
|
|
<p id="elb_pro_0006__p31765646171442">This makes ELB a good choice for running services that require high reliability, such as websites and toll collection systems.</p>
|
|
<div class="fignone" id="elb_pro_0006__fig158310309337"><span class="figcap"><b>Figure 3 </b>Eliminating SPOFs</span><br><span><img class="vsd" id="elb_pro_0006__image762485204912" src="en-us_image_0000001794660601.png"></span></div>
|
|
</div>
|
|
<div class="section" id="elb_pro_0006__section220419419265"><h4 class="sectiontitle">Cross-AZ Load Balancing</h4><p id="elb_pro_0006__p4089950317155">ELB can distribute traffic across AZs. When an AZ becomes faulty, ELB distributes traffic across backend servers in other AZs.</p>
|
|
<p id="elb_pro_0006__p99690131295">ELB is ideal for banking, policing, and large application systems that require high availability.</p>
|
|
<div class="fignone" id="elb_pro_0006__fig539117712156"><span class="figcap"><b>Figure 4 </b>Traffic distribution to servers in one or more AZs</span><br><span><img class="vsd" id="elb_pro_0006__image9155182417491" src="en-us_image_0000001794819713.png"></span></div>
|
|
</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>
|
|
|