Shulou(Shulou.com)05/31 Report--

This article introduces the practice of load balancing and routing policy configuration of application traffic in serverless SAE scenario. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

Traffic management from case-oriented to application-oriented

In Serverless scenario, due to flexibility and changeability of underlying computing instances, backend application instances need to be frequently online and offline, so the traditional load balancing management method in ECS scenario is no longer suitable.

SAE products provide users with application-oriented traffic management, which no longer needs to care about elastic scenarios and instances of publishing scenarios, but only needs to care about the configuration of monitoring and the health check probes of application instances, and hand over the complex instance-oriented configuration to SAE products.

Load balancing configuration of single application

For individual applications, SAE products support exposing application services through public or private network SLB instance snooping. Currently, only TCP protocol is supported. Considering the need of HTTPS transformation for traditional HTTP applications, SAE also supports the configuration of HTTPS snooping, so that HTTP servers can provide HTTPS services without modification.

The specification fee and traffic fee will be generated when the public network SLB is used for Internet client access, while the specification fee will be incurred when the private network SLB is used for client access within the VPC.

In order to enable SAE products to accurately control the time when instances go online, users need to configure probes correctly during deployment to avoid business losses.

Multi-application routing policy configuration

In practice, large and medium-sized enterprises often split their business into different applications or services, such as login services, billing services and other highly related parts, separately into applications, independent R & D and operation and maintenance. and then exposed through a unified gateway service, for users, it is like using a single application.

SAE provides SLB instance-based gateways that forward traffic to different application instances according to domain name and HTTP Path, and functionally target Nginx gateways in the industry.

The gateway implemented by the public network SLB instance for Internet client access will incur both specification fee and traffic fee, while the gateway implemented by the private network SLB instance will incur specification fee for client access within the VPC.

Self-built micro-service gateway

For micro-service gateways that are common in micro-service scenarios, SAE does not provide product support, but users are still free to deploy self-built micro-service gateways in the middle of SAE.

In practice, the micro-service gateway can also be deployed in SAE as an application. The micro-service gateway forwards the business traffic to the instance that provides the micro-service according to the user-defined configuration. As an application, micro-service gateway can also expose services to public and private networks through SLB instances.

This is the end of the practice of load balancing and routing policy configuration of application traffic in the serverless SAE scenario. I hope the above content can be of some help and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.