If you use Enterprise Distributed Application Service (EDAS) to host applications on Elastic Compute Service (ECS) clusters, you can bind Server Load Balancer (SLB) instances to the applications. Then, EDAS distributes traffic to multiple backend ECS instances based on forwarding policies. This improves the service capability and availability of the applications. The changes you made to the SLB instances bound to applications in the EDAS console can be synchronized to the SLB console. You do not need to make the changes again in the SLB console.
Listeners distribute requests to backend servers. After you bind SLB instances to the applications that are hosted on ECS clusters in EDAS, you must configure listeners for the SLB instances. For more information, see Listener overview.
You can configure Layer 4 TCP or Layer 7 HTTP listeners for the applications that are hosted on ECS clusters based on your needs.
- TCP is applicable to scenarios that require high reliability and data accuracy but medium data transfer speed. For example, you can use TCP to transmit files, send or receive emails, and perform remote logons.
- HTTP is applicable to applications that need to identify data content, such as web applications and small mobile games.
EDAS provides multiple SLB solutions to distribute traffic in different scenarios.
|Configure a dedicated SLB instance for an application.||Configure a dedicated SLB instance for an application|
|Configure URL forwarding policies for application instance groups.||Use URLs to distribute traffic to application instance groups|
|Configure a listening port for multiple applications.||Configure a listening port for multiple applications|
|Configure a domain name or a URL for multiple applications.||Use a shared SLB instance and dedicated domain names or URLs to distribute traffic|