Cloud service access method and apparatus, and access request processing method and apparatus

Abstract

The present disclosure provides a cloud service access method and apparatus, and an access request processing method and apparatus. The cloud service access method comprises: sending an access request to a service load balancing server by means of a first terminal node; acquiring an IP address of a second terminal node returned by the service load balancing server in response to the access request; and upon receiving packet data, accessing a private network connection service by means of the IP address, and using the private network connection service to send the packet data to a load balancing service, so that the load balancing service can send the packet data to a backend server on the basis of cloud service information and configuration information. In embodiments of the present disclosure, packet data is sent to a private network connection service on the basis of an IP address of a second terminal node, a load balancing service is used for implementing traffic distribution, without needing to configure addresses of backend servers in VPCs of clients, thereby reducing the occupation of the addresses in the VPCs of the clients by the backend servers, and saving address resources of the clients.

Description

[0001] This disclosure relates to the field of cloud computing technology, and in particular to a cloud service access method and apparatus, and an access request processing method and apparatus. Background Technology: In microservice scenarios, cloud services are typically accessed via client-side load balancing (the client directly obtains the backend server address from the load balancer) rather than through a dedicated load balancer. To achieve client-side load balancing, an SDK (Software Development Kit) needs to be installed on the client. The SDK sends requests to the microservice's load balancing component, which then sends the backend server IP address (Internet Protocol Address) that the client needs to access to the client. The client then sends the request directly to the backend server through the SDK. In this model, when multiple microservice clients simultaneously access the same cloud service, each client needs to access the cloud service's backend server address within its own VPC (Virtual Private Cloud). Address connectivity is typically achieved through an address mapping component, requiring each backend server address to occupy an address within a client's VPC. When there are a large number of cloud service backend servers, a large number of addresses need to be occupied within the user's VPC. Users are often unable to provide the corresponding addresses due to limited address resources. This invention discloses a cloud service access method and apparatus, and an access request processing method and apparatus, to reduce the backend servers' occupation of addresses within the client's VPC and save the client's address resources.In a first aspect, embodiments of this disclosure provide a cloud service access method applied to a client. The client and a microservice are connected via a communication connection. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network (VPC), and the microservice is configured with a second VPC. The first VPC contains a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service connects the first VPC and the second VPC. The method includes: sending an access request to the business load balancing server through the first terminal node; obtaining the IP address of the second terminal node returned by the business load balancing server in response to the access request; upon receiving message data, accessing the private network connection service through the IP address, and using the private network connection service to send the message data to the load balancing service, so that the load balancing service sends the message data to the backend server according to cloud service information and configuration information. The message data carries cloud service information, which is used to determine the cloud service to be accessed. The configuration information is returned to the load balancing service by the business load balancing server in response to the access request. Secondly, this disclosure provides an access request processing method applied to a microservice, wherein the microservice and a client are connected in communication. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network, and the microservice is configured with a second private network. The first private network is configured with a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service is used to connect the first private network and the second private network. The method includes: in response to receiving an access request from the client, sending the IP address of the second terminal node to the client using the business load balancing server, and sending configuration information to the load balancing service so that the client accesses the private network connection service through the IP address; sending the message data to the load balancing service using the private network connection service; wherein the message data carries cloud service information, the cloud service information is used to determine the cloud service to be accessed, and the configuration information is returned by the business load balancing server to the load balancing service in response to the access request. The load balancing service is used to send the message data to the backend server based on the cloud service information and the configuration information.Thirdly, this disclosure provides a cloud service access device applied to a client. The client and a microservice are communicatively connected. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network (VPC), and the microservice is configured with a second VPC. The first VPC contains a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service connects the first VPC and the second VPC. The device includes: a request module configured to send an access request to the business load balancing server through the first terminal node; an acquisition module configured to acquire the IP address of the second terminal node returned by the business load balancing server in response to the access request; and an access module configured to, upon receiving message data, access the private network connection service through the IP address and use the private network connection service to send the message data to the load balancing service, so that the load balancing service sends the message data to the backend server according to cloud service information and configuration information, wherein the message data carries the cloud service information. The cloud service information is used to determine the cloud service to be accessed, and the configuration information is returned by the business load balancing server to the load balancing service in response to the access request. Fourthly, this disclosure provides an access request processing apparatus. The microservice and client are communicatively connected. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network (VPC), and the microservice is configured with a second VPC. The first VPC contains a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service connects the first VPC and the second VPC. The apparatus includes: a control module configured to, in response to receiving an access request from a client, send the IP address of the second terminal node to the client using the business load balancing server, and send configuration information to the load balancing service, so that the client accesses the private network connection service via the IP address. The private network connection service sends the message data to the load balancing service, wherein the message data carries cloud service information used to determine the cloud service to be accessed, and the configuration information is returned by the business load balancing server to the load balancing service in response to the access request; and a load balancing module. It is configured to use the load balancing service to send the message data to the backend server based on the cloud service information and the configuration information.Fifthly, embodiments of this disclosure provide an electronic device, including: a processor; and a memory storing a program, wherein the program includes instructions that, when executed by the processor, implement the method described above. Sixthly, embodiments of this disclosure provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described above. Seventhly, embodiments of this disclosure provide a computer program product including a computer program that, when executed by a processor, implements the method steps described above. Compared with existing technologies, this disclosure has the following advantages: In embodiments of this disclosure, an application is made to a client, where the client and a microservice are connected. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network (VPC), and the microservice is configured with a second VPC. The first VPC contains a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service connects the first VPC and the second VPC. The method includes: sending an access request to the business load balancing server through the first terminal node; obtaining the IP address of the second terminal node returned by the business load balancing server in response to the access request; upon receiving message data, accessing the private network connection service through the IP address, and using the private network connection service to send the message data to the load balancing service, so that the load balancing service sends the message data to the backend server according to cloud service information and configuration information. The message data carries cloud service information, which is used to determine the cloud service to be accessed. The configuration information is returned by the service load balancing server to the load balancing service in response to the access request. This embodiment of the disclosure sends packet data to the private network connection service based on the IP address of the second terminal node, and then combines this with the load balancing service to distribute traffic. It eliminates the need to configure the addresses of each backend server within the client's VPC, reducing the address space occupied by backend servers within the client's VPC and saving client address resources. The above description is merely an overview of the technical solution of this disclosure. To better understand the technical means of this disclosure, it can be implemented according to the contents of the specification. Furthermore, to make the above and other objects, features, and advantages of this disclosure more apparent, specific embodiments of this disclosure are described below. Brief Description of the Drawings: In the drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements.These accompanying drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments according to this disclosure and should not be considered as limiting the scope of this disclosure. Figure 1 is a flowchart of a cloud service access method provided by an embodiment of this disclosure; Figure 2 is a schematic diagram of an existing cloud service access process; Figure 3 is a schematic diagram of a cloud service access process provided by an embodiment of this disclosure; Figure 4 is a flowchart of an access request processing method provided by an embodiment of this disclosure; Figure 5 is a structural block diagram of a cloud service access device provided by an embodiment of this disclosure; Figure 6 is a structural block diagram of an access request processing device provided by an embodiment of this disclosure; Figure 7 is a structural block diagram of an electronic device used to implement an embodiment of this disclosure. Detailed Description In the following, only some exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the concept or scope of this disclosure. Therefore, the drawings and descriptions are considered exemplary in nature and not restrictive. To facilitate understanding of the technical solutions of the embodiments of this disclosure, the related technologies of the embodiments of this disclosure are described below. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this disclosure, all of which fall within the protection scope of the embodiments of this disclosure. The terms involved are explained below. Microservices (or microservice architecture) are a cloud-native architectural approach that includes numerous loosely coupled, independently deployable small components or services within a single application. These services typically have their own technology stack, including databases and data management models; communicate with each other through a combination of a REST API (Representational State Transfer Application Programming Interface, a web application programming interface designed according to the REST architectural style), event streams, and message brokers; and are organized according to business capabilities, with service delimiters often referred to as bounded contexts. Microservice scenarios refer to specific business environments or problem domains where microservice architecture is designed and implemented in real-world applications.In existing solutions, when accessing cloud services in a microservices scenario, refer to Figure 2, which illustrates the existing cloud service access process. This diagram shows the interaction between two clients and the microservice, specifically including the following steps: For each client, the client accesses the load balancer through an endpoint within the client's VPC (Virtual Private Cloud). The load balancer sends the backend server's IP address (Internet Protocol Address) to the client. The client then accesses the backend server through the endpoint in the VPC. During this process, each backend server needs to create a corresponding endpoint within the user's VPC, and each endpoint occupies one IP address within the user's VPC. When there are many backend servers, this requires a large number of addresses within the client's VPC, while the user's VPC cannot provide a corresponding number of IP addresses. Based on this, this disclosure provides a cloud service access method and apparatus, and an access request processing method and apparatus. This method can aggregate backend server addresses in a microservice scenario, requiring only one address within a Client VPC, thus reducing the occupancy of addresses within the Client VPC. Furthermore, this disclosure can use client load balancing to access cloud services, i.e., the client accesses the backend load balancing server and directly obtains the backend server address. By installing an SDK (Software Development Kit) on the client, the client can directly send requests to the backend server through the SDK, without requiring client SDK upgrades, thereby ensuring system stability and compatibility. This disclosure provides a cloud service access method applicable to cloud service access in microservice scenarios. In this disclosure, microservice scenarios may include, but are not limited to: e-commerce systems, financial service platforms, media streaming services, smart IoT platforms, and medical information systems. Figure 1 is a flowchart of a cloud service access method provided in this disclosure embodiment. As shown in Figure 1, the method includes: Step S101, sending an access request to the business load balancing server through the first terminal node. The method is applied to a client, which is configured with a first private network, in which a first terminal node of a service load balancing server and a second terminal node of a private network connection service are configured.In this embodiment, the client can initiate requests to the microservice, including data operations, queries, transaction processing, etc. The microservice responds to these requests, providing the required data or executing the requested operations, and returns the results to the client. The client can include, but is not limited to, web browsers, mobile applications, desktop applications, and other services. The microservice includes a business load balancer server, one or more backend servers, and a load balancing service. The business load balancer server can be software or hardware running on a general-purpose server. The business load balancer server can be used to implement load balancing control. The load balancing service is a cloud service provided by the microservice, which can be used to forward traffic to the backend servers. Servers are physical hardware devices, including computers and their storage, processors, memory, and other components. They can run various software to process and store data and provide services to client devices. Servers can be physical servers, i.e., actual existing machines, or virtual servers, which are logical partitions created on physical servers through virtualization technology. When determining the type of server used to implement the cloud service, factors such as application type, concurrency, data processing requirements, and performance requirements can be considered. A Virtual Private Cloud (VPC) is used to build a logically isolated cloud data center. A VPC consists of logical network devices (such as virtual routers and virtual switches) and can form an on-demand customized network environment with traditional data centers via leased lines / VPNs (Virtual Private Networks), enabling smooth application migration to the cloud. A VPC is a user-created custom private network based on the cloud. Different VPCs are logically isolated at Layer 2. Users can create and manage cloud product instances within their own VPCs. In this embodiment, the VPC configured by the client is designated as the first VPC, and the VPC configured by the microservice is designated as the second VPC. By establishing a secure channel between the first and second VPCs, data security during transmission is ensured, avoiding potential security risks caused by public network exposure. Service providers can create endpoint services, allowing other customers within the VPC to establish private network connections with their services by creating endpoints. The first private network (VPC) is configured with a first terminal node that serves as a load balancer for the microservice and a second terminal node that provides a private network connection service. The first terminal node is a network component configured to provide an interface for accessing the load balancer for the microservice. The second terminal node is a network component configured to provide an interface for accessing the private network connection service.Both the first and second terminal nodes are elastic network interfaces with private IP addresses. As the communication entry point for interface-type terminal node services, they can directly communicate with resources within the VPC without additional routing or gateway configuration. PrivateLink (PVL) enables a secure and stable private connection between the VPC and cloud services, simplifying the network architecture, enabling private network access services, and avoiding potential security risks associated with accessing services through the public network. The private link service can be a cloud service used to connect the client VPC to the microservice VPC; that is, the private link service connects the first VPC to the second VPC of one or more backend servers. In this embodiment, the client sends an access request to the microservice load balancer server within the client VPC via the microservice load balancer server on the first terminal node. Step S102: Obtain the IP address of the second terminal node returned by the load balancer server in response to the access request. In this embodiment, the microservice load balancer server is a service provided by the cloud service provider to the user for controlling load balancing. The load balancing server on the microservice side returns the IP address of the second terminal node based on the received access request from the client. The IP address of the second terminal node is used to locate the second terminal node within the client's VPC. In step S103, upon receiving packet data, the private network connection service is accessed through the IP address. The packet data is then sent to the load balancing service using the private network connection service. This allows the load balancing service to send the packet data to the backend server based on cloud service information and configuration information. The packet data carries cloud service information, which is used to determine the cloud service to be accessed. The configuration information is returned to the load balancing service by the business load balancing server in response to the access request. In this embodiment, after obtaining the IP address of the second terminal node, the second terminal node is located based on this IP address, and the received packet data is sent to the private network connection service. The private network connection service enables the connection between the first and second VPCs. Therefore, it can be used to send packet data to a load balancing service, which then forwards the packet data to the backend server based on cloud service information and configuration details. The load balancing service can also be used to distribute received packet data to servers on the microservice side.The load balancing service can be a pre-defined microservice. For example, this microservice can be used to implement load balancing, supporting ultra-high performance and automatic elasticity. A single instance can handle 100 million concurrent connections to cope with high-concurrency business. The specific choice can be made according to actual needs, and this disclosure does not impose specific limitations. In an optional implementation, the microservice can also be a load balancing service specifically designed for application-layer load scenarios, possessing strong elasticity and large-scale application-layer traffic processing capabilities. The configuration information of the load balancing service can include the IP address information of the load balancing service, as well as the correspondence between cloud services and servers. Cloud services are a service delivery model based on the Internet, allowing users to access shared computing resources on demand, including but not limited to servers, storage, databases, networks, software, analytics, etc., without directly managing the underlying hardware. The configuration information can be used to configure the correspondence between cloud services and servers. It's important to note that different cloud services require different types or configurations of servers. Below are some major cloud service types and their server requirements: Infrastructure as a Service (IaaS): Provides virtualized computing resources, such as virtual servers. Depending on user needs, these servers can be configured with different CPU (Central Processing Unit), memory, storage, and network resources. Although the underlying physical server cluster is the same, each IaaS instance can be customized according to specific application needs through a virtualization layer. Platform as a Service (PaaS): Further abstracts on top of IaaS, providing a platform for application development and deployment. This requires servers with specific configurations, including pre-installed operating systems, middleware, databases, etc., to support specific development frameworks or languages. For example, a PaaS running Java applications requires servers with an optimized Java runtime environment and related services. Software as a Service (SaaS): Provides applications directly to users, typically without requiring users to concern themselves with the underlying server configuration. Nevertheless, the server configuration behind a SaaS application still needs to be carefully designed based on the application's characteristics and scale (such as the number of users and data processing requirements), involving advanced configurations such as load balancing and high-availability clusters.Functions as a Service (FaaS) allows users to run code snippets without managing servers and is not directly concerned with the specific type of server, but it requires a highly optimized server environment to quickly respond to event triggers and execute functions. By identifying information in the message data, the information of the cloud service the user wants to access can be obtained; that is, the message data carries information about the cloud service to be accessed. This cloud service information can be the name, ID (identifier), or IP address of the cloud service, which can be used to identify the cloud service to be accessed. In this step, the client's VPC only needs to configure a second terminal node for the private network connection service. Based on the IP address of the second terminal node, the message data can be sent to the private network connection service. The message data is generated by the client based on the cloud service the user wants to access; that is, the message data carries information about the cloud service to be accessed. This step reduces the number of terminal node IP addresses that need to be configured within the client's VPC. Regardless of the number of backend servers, message data forwarding can be achieved solely based on the IP address of the second terminal node. In this embodiment of the disclosure, the cloud service information to be accessed can be determined based on the message data, and the server and server address information corresponding to the cloud service can be determined based on the configuration information. The load balancing service determines the backend server for receiving the message data according to the message data and the configuration information, and then sends the message data to the backend server.This embodiment of the disclosure is applied to a client, wherein the client and a microservice are connected for communication. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network, and the microservice is configured with a second private network. The first private network is configured with a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service is used to connect the first private network and the second private network. The method includes: sending an access request to the business load balancing server through the first terminal node; obtaining the IP address of the second terminal node returned by the business load balancing server in response to the access request; upon receiving packet data, accessing the private network connection service through the IP address, and using the private network connection service to send the packet data to the load balancing service, so that the load balancing service sends the packet data to the backend server according to cloud service information and configuration information. The packet data carries the cloud service information, which is used to determine the cloud service to be accessed, and the configuration information is returned by the business load balancing server to the load balancing service in response to the access request. This disclosure embodiment sends packet data to the private network connection service based on the IP address of the second terminal node, and then combines it with the load balancing service to distribute traffic. This eliminates the need to configure the addresses of each backend server within the client's VPC, reducing the address space occupied by backend servers within the client's VPC and saving client address resources. In an optional implementation, sending an access request to the business load balancing server through the first terminal node includes: generating an access request according to a specified method; and sending the access request to the first terminal node, so that the access request is sent to the business load balancing server through the first terminal node. In this disclosure embodiment, the specified method is a pre-determined access request generation method, for example, including but not limited to: using API (Application Programming Interface), SDK (Software Development Kit), CLI (Command-Line Interface) tools, console, or custom code to construct a request to the cloud service.This request typically includes an HTTP (Hypertext Transfer Protocol) method, necessary parameters, authentication information, and a target URL (Uniform Resource Locator), the latter containing information about the endpoint. In an optional implementation, the client is configured with an SDK tool to generate the access request in a specified manner, including generating the access request based on the SDK tool. In this optional implementation, for microservice scenarios, the client is configured with an SDK tool, in which case the access request can be generated based on the SDK tool. Even when the number of cloud service backend servers is very large, there is no need to upgrade the client's SDK. In this embodiment, an SDK is installed on the client and load balancing is implemented based on the SDK. A list of active service instances is maintained on the client, including information about the first endpoint. The SDK is configured to know the addresses (IPs and ports) of all available service instances. This can be achieved through static configuration or by using a service discovery mechanism (such as Eureka, Consul, Zookeeper, etc.). Based on the configured service instance list, the IP address of the first terminal node is determined, and an access request is sent to the load balancer server of the microservice through the first terminal node. It should be noted that when a client accesses a cloud service, the service provider may require the client to upgrade its SDK to switch to a regular load balancer instead of a service load balancer. However, regular load balancing cannot dynamically allocate traffic based on real-time business data and backend server resource usage. Furthermore, once the client's SDK is installed, upgrades are highly dependent, and most service providers will not require users to upgrade their SDKs. In this embodiment, an access request can be sent to the load balancer server of the microservice based on the client's already installed SDK, without requiring the client to upgrade its SDK. In one optional implementation, accessing the private network connection service via the IP address and sending the packet data to the load balancing service using the private network connection service can be performed according to the following steps: accessing the second terminal node based on the IP address; sending the packet data to the private network connection service through the second terminal node, so that the private network connection service sends the packet data to the load balancing service.In this optional implementation, the second terminal node occupies only one IP address within the client's VPC. Accessing the second terminal node based on this IP address enables access to the private network connection service, thereby sending packet data to the private network connection service. This allows access to the backend server using the private network connection service and load balancing service. In this step, the backend server of the microservice is exposed to the client's VPC using the private network connection service, eliminating the need to configure the IP addresses of each backend server within the VPC, thus enabling traffic forwarding to the backend server. Figure 3 is a schematic diagram of a cloud service access process provided by an embodiment of this disclosure. The implementation process of this method will be described in detail below with reference to Figure 3. The method may specifically include the following steps:

[0002] 1. The client accesses the load balancer through its endpoint within the Client VPC, which is the first terminal node. The load balancer then sends the IP address of the endpoint within the Client VPC connected to the private network to the client. This private network connection is a microservice that can be invoked by the client.

[0003] 2. The service load balancer sends the backend load balancer address selected by the user to the NLB (Network Load Balancer), which is the load balancing service;

[0004] 3. The client accesses the backend server by accessing the PVL endpoint in the Client VPC (EP in Figure 3), which is the second terminal node;

[0005] 4. After receiving the Client request, the private network connection and NLB forward the Client traffic to the backend server based on the information provided by the business load balancer. Based on the above steps, in a microservice scenario, when accessing cloud services, the Client VPC only needs to occupy one IP address to access all backend servers. In addition, this method does not require upgrading the client's SDK. This disclosure provides a cloud service access method and an access request processing method. This method exposes the backend servers of the microservice to the Client VPC by using PVL, which greatly reduces the number of addresses occupied in the Client VPC and does not require the business to upgrade the Client's SDK. As can be seen from the above description, the client can send packet data to the private network connection service based on the IP address of the second terminal node, and then combine the load balancing service to realize traffic distribution. There is no need to configure the addresses of each backend server in the client's VPC, which can reduce the occupation of backend server addresses in the client's VPC and save client address resources. The above description is all from the client's perspective. The following is an explanation from the perspective of the microservice. Figure 4 is a flowchart of an access request processing method provided by an embodiment of this disclosure. The steps involved in Figure 4 are explained below. This disclosure also provides an access request processing method applied to a microservice, wherein the microservice and a client are connected in communication. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network, and the microservice is configured with a second private network. The first private network is configured with a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service is used to connect the first private network and the second private network. The method includes: step S401, in response to receiving an access request from the client, the business load balancing server sends the IP address of the second terminal node to the client and sends configuration information to the load balancing service, so that the client accesses the private network connection service through the IP address. The private network connection service sends message data to the load balancing service, wherein the message data carries cloud service information, the cloud service information is used to determine the cloud service to be accessed, and the configuration information is returned by the business load balancing server to the load balancing service in response to the access request. Step S402: The load balancing service sends the message data to the backend server based on the cloud service information and the configuration information. In this embodiment, the method is applied to a microservice.The microservice architecture includes a business load balancer server, one or more backend servers, and a load balancing service. The business load balancer server can be software or hardware running on a general-purpose server. It is configured to control load balancing. The load balancing service is a cloud service provided by the microservice architecture, used to forward traffic to the backend servers. Servers are physical hardware devices, including computers and their storage, processors, memory, and other components. They run various software programs to process and store data and provide services to client devices. Servers can be physical servers (actually existing machines) or virtual servers (logical partitions created on physical servers using virtualization technology). When determining the type of server used to implement the cloud service, factors such as application type, concurrency, data processing requirements, and performance requirements can be considered. The client is configured with a first private network (VPC), which contains a first terminal node of the business load balancer server and a second terminal node of the private network connection service. The client can send requests to the microservice architecture, including data operations, queries, and transaction processing. The microservice responds to these requests, providing the necessary data or performing the requested operations, and returns the results to the client. Clients can include, but are not limited to, web browsers, mobile applications, desktop applications, and other services. A Virtual Private Cloud (VPC) is used to build a logically isolated cloud data center. A VPC consists of logical network devices (such as virtual routers and virtual switches) and can form an on-demand customized network environment with traditional data centers via dedicated lines / VPNs (Virtual Private Networks), enabling smooth application migration to the cloud. A VPC is a user-created custom private network based on the cloud. Different VPCs are logically isolated at Layer 2, and users can create and manage cloud product instances within their own VPCs. In this embodiment, the VPC configured by the client is designated as the first VPC, and the VPC configured by the microservice is designated as the second VPC. By establishing a secure channel between the first and second VPCs, data security during transmission is ensured, avoiding potential security risks caused by public network exposure. Service providers can create endpoint services, allowing other customers within a VPC to establish private network connections with their services by creating endpoints. The first endpoint in the first VPC is configured with a microservice-side load balancer, and the second endpoint is configured with a private network connection service.In this embodiment, the first terminal node is a network component configured to provide an interface for accessing the load balancer server of the microservice. The second terminal node is a network component configured to provide an interface for accessing the private network connection service. Private Link (PVL) enables a secure and stable private connection between a Virtual Private Cloud (VPC) and cloud services, simplifying the network architecture, enabling private network access services, and avoiding potential security risks associated with accessing services via the public network. The private network connection service can be a cloud service used to establish a connection between the client VPC and the microservice VPC; that is, the private network connection service connects the first VPC and the one or more backend server second VPCs. In this embodiment, the client sends an access request to the load balancer server of the microservice via the first terminal node within the client VPC. In this embodiment, the microservice load balancer server is a service provided by the cloud service provider to the user for controlling business load balancing. The load balancing server on the microservice side returns the IP address of the second terminal node based on the received access request from the client. This IP address is used to locate the second terminal node within the client's VPC. The load balancing service can distribute the received access requests to the servers on the microservice side. The load balancing service can be a pre-defined microservice; for example, this microservice can be used to implement load balancing, supporting ultra-high performance and automatic elasticity, with a single instance capable of handling 100 million concurrent connections to cope with high-concurrency business. The specific choice can be made according to actual needs, and this disclosure does not impose specific limitations. In an optional implementation, the microservice can also be a load balancing service specifically designed for application-layer load scenarios, possessing strong elasticity and large-scale application-layer traffic processing capabilities. Microservices are an architectural style that advocates developing a single application as a set of small services, each running in its own process and communicating with each other using lightweight communication mechanisms. Each service is built around a specific business function, can be deployed and scaled independently, and can be independently understood, developed, and tested. The configuration information for a load balancing service may include the IP address information of the load balancing service, as well as the mapping between cloud services and servers. Cloud services are a series of computing resources and services provided via the internet. These resources and services may include, but are not limited to: Infrastructure as a Service (IaaS): such as virtual machines, storage space, network bandwidth, etc., allowing users to rent hardware resources.Platform as a Service (PaaS): Provides a platform on which users can build, test, and run applications without managing the underlying infrastructure. Software as a Service (SaaS): Delivers software applications directly over the internet, allowing users to use them without installation. Function as a Service (FaaS) or Serverless: Users only need to write and deploy code snippets or functions without worrying about the runtime environment. In this embodiment, after obtaining the IP address of the second terminal node, the second terminal node is located based on that IP address, and the received message data is sent to the private network connection service. By identifying the information in the message data, the information of the cloud service to be accessed by the user can be obtained; that is, the message data carries information about the cloud service to be accessed. The cloud service information can be the name, ID, or IP address of the cloud service, which can be used to identify the cloud service to be accessed. In this step, the client's VPC only needs to be configured with the second terminal node of the private network connection service; based on the IP address of the second terminal node, message data can be sent to the private network connection service. This step reduces the number of IP addresses of the terminal nodes that need to be configured within the client's VPC. Regardless of the number of backend servers, packet forwarding can be achieved solely based on the IP address of the second terminal node. In this embodiment, the cloud service information to be accessed can be determined based on the packet data, and the server and server address information corresponding to the cloud service can be determined based on the configuration information. The load balancing service determines the backend server for receiving the packet data based on the packet data and the configuration information, and then sends the packet data to the backend server. In this embodiment, packet data is sent to the private network connection service based on the IP address of the second terminal node, and traffic distribution is achieved in conjunction with the load balancing service. There is no need to configure the addresses of each backend server within the client's VPC, which reduces the address occupation of the client's VPC by the backend servers and saves the client's address resources. In one optional implementation, the configuration information is used to configure the server corresponding to the cloud service; sending the message data to the backend server based on the cloud service information and the configuration information can be performed according to the following steps: determining the cloud service to be accessed based on the message data; determining the target IP address corresponding to the cloud service to be accessed based on the configuration information; and sending the message data to the server corresponding to the target IP address. In this embodiment, the configuration information includes the correspondence between cloud services and servers, and the server corresponding to the cloud service is configured to implement the cloud service; that is, the configuration information is used to configure the server corresponding to the cloud service.The message data may carry data to identify the cloud service to be accessed, such as the name of the cloud service and its identification code. The load balancing service determines the target IP address corresponding to the cloud service to be accessed based on the configuration information. In this step, the load balancing service can distribute the message data to the backend server. In an optional implementation, determining the target IP address corresponding to the cloud service to be accessed based on the configuration information can be performed as follows: Based on the configuration information, determine the IP address of the server corresponding to the cloud service to be accessed; determine the target IP address from the server's IP address. In this embodiment, the configuration information may include the IP address corresponding to the server. The cloud service to be accessed may correspond to multiple servers, and the target server can be determined from these multiple servers. The target server is the server selected by the load balancing service to implement the cloud service to be accessed, and the IP address of the target server is used as the target IP address. It should be noted that the configuration information can be preset according to actual needs and returned to the client by the load balancing server on the microservice side in response to the client's access request. In one optional implementation, determining the target IP address from the server's IP addresses can be performed by: randomly determining the target IP address from the server's IP addresses, or using the IP address of an idle server as the target IP address. In this embodiment, considering the need for more rational allocation of backend servers, the target IP address can be randomly determined from the server's IP addresses, or the IP address of an idle server can be used as the target IP address, in order to fully utilize backend server resources. Corresponding to the application scenario and method of the cloud service access method provided in this embodiment, this embodiment also provides a cloud service access device.Figure 5 is a structural block diagram of a cloud service access device provided in an embodiment of this disclosure. This device is applied to a client, which is communicatively connected to a microservice. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network (VPC), and the microservice is configured with a second VPC. The first VPC contains a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service connects the first VPC and the second VPC. As shown in Figure 5, the device includes: a request module 501, configured to send an access request to the business load balancing server through the first terminal node; an acquisition module 502, configured to acquire the IP address of the second terminal node returned by the business load balancing server in response to the access request; and an access module 503, configured to access the private network connection service through the IP address when receiving message data, and use the private network connection service to send the message data to the load balancing service, so that the load balancing service sends the message data to the backend server according to cloud service information and configuration information. The message data carries cloud service information, which is used to determine the cloud service to be accessed. The configuration information is returned by the service load balancing server to the load balancing service in response to the access request. This embodiment sends message data to the private network connection service based on the IP address of the second terminal node, and then combines this with the load balancing service to distribute traffic. This eliminates the need to configure the addresses of each backend server within the client's VPC, reducing the address space occupied by backend servers within the client's VPC and saving client address resources. In one optional embodiment, sending an access request to the service load balancing server through the first terminal node includes: generating an access request according to a specified method; and sending the access request to the first terminal node, so that the access request is sent to the service load balancing server through the first terminal node. In another optional embodiment, the client is configured with an SDK tool to generate the access request according to a specified method, including: generating the access request based on the SDK tool. In one optional implementation, accessing the private network connection service via the IP address and sending the packet data to the load balancing service using the private network connection service includes: accessing the second terminal node based on the IP address; and sending the packet data to the private network connection service via the second terminal node, so that the private network connection service sends the packet data to the load balancing service.The functions of each module in the apparatus of this disclosure embodiment can be found in the corresponding description in the above method, and they have corresponding beneficial effects, which will not be repeated here. Corresponding to the application scenarios and methods of the access request processing method provided in this disclosure embodiment, this disclosure embodiment also provides an access request processing apparatus. Figure 6 is a structural block diagram of an access request processing device provided in an embodiment of this disclosure. This device is applied to a microservice, which is communicatively connected to a client. The microservice includes a business load balancing server, one or more backend servers, and a load balancing service. The client is configured with a first private network (VPC), and the microservice is configured with a second VPC. The first VPC contains a first terminal node of the business load balancing server and a second terminal node of a private network connection service. The private network connection service connects the first VPC and the second VPC. As shown in Figure 6, the device includes a control module 601, configured to, in response to receiving an access request from a client, send the IP address of the second terminal node to the client using the business load balancing server, and send configuration information to the load balancing service, so that the client accesses the private network connection service through the IP address. The private network connection service then sends the message data to the load balancing service. The message data carries cloud service information, which is used to determine the cloud service to be accessed. The configuration information is returned by the service load balancing server to the load balancing service in response to the access request; the load balancing module 602 is configured to use the load balancing service to send the packet data to the backend server according to the cloud service information and the configuration information. In this embodiment, packet data is sent to the private network connection service based on the IP address of the second terminal node, and traffic distribution is achieved in combination with the load balancing service. It is not necessary to configure the addresses of each backend server in the client's VPC, which can reduce the occupation of the client's VPC address by the backend server and save the client's address resources. In an optional implementation, the configuration information is used to configure the server corresponding to the cloud service; sending the packet data to the backend server according to the cloud service information and the configuration information includes: determining the cloud service to be accessed according to the packet data; determining the target IP address corresponding to the cloud service to be accessed based on the configuration information; and sending the packet data to the server corresponding to the target IP address.In one optional implementation, determining the target IP address corresponding to the cloud service to be accessed based on the configuration information includes: determining the IP address of the server corresponding to the cloud service to be accessed based on the configuration information; and determining the target IP address from the server's IP address. In another optional implementation, determining the target IP address from the server's IP address includes: randomly determining the target IP address from the server's IP address, or using the IP address of a server in an idle state as the target IP address. The functions of each module in each device of this disclosure embodiment can be referred to the corresponding description in the above method, and have corresponding beneficial effects, which will not be repeated here. This disclosure embodiment also provides an electronic device, including: at least one processor; and a memory communicatively connected to at least one processor. The memory stores a computer program that can be executed by the at least one processor, and the computer program, when executed by the at least one processor, is used to cause the electronic device to perform the method of this disclosure embodiment. Figure 7 is a structural block diagram of an electronic device used to implement the embodiments of this disclosure. As shown in Figure 7, the electronic device includes: a memory 710 and a processor 720, and the memory 710 stores a computer program that can run on the processor 720. When the processor 720 executes the computer program, it implements the method described in the above embodiments. The number of memory 710 and processor 720 can be one or more. The electronic device also includes a communication interface 730 for communicating with external devices and performing data exchange and transmission. If the memory 710, processor 720, and communication interface 730 are implemented independently, they can be interconnected via a bus to complete communication with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 7, but this does not indicate that there is only one bus or one type of bus.Optionally, in specific implementations, if the memory 710, processor 720, and communication interface 730 are integrated on a single chip, then the memory 710, processor 720, and communication interface 730 can communicate with each other through an internal interface. This disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in this disclosure. This disclosure also provides a computer program product, including a computer program, wherein the computer program, when executed by a computer's processor, is used to cause the computer to perform the methods of this disclosure. This disclosure further provides a chip including a processor for calling and executing instructions stored in a memory, causing a communication device with the chip installed to perform the methods provided in this disclosure. This disclosure also provides a chip including an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory, and when the code is executed, the processor is used to perform the methods provided in this disclosure. It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting Advanced Reduced Instruction Set Machines (ARM) architecture. Further, optionally, the aforementioned memory can include read-only memory and random access memory. This memory can be volatile memory or non-volatile memory, or it can include both volatile and non-volatile memory.Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available. For example, static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), and enhanced synchronous dynamic random access memory.

[0006] SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM) OIn the above embodiments, implementation can be achieved, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to this disclosure is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. In the description of this specification, references to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this disclosure. Moreover, the specific features, structures, materials, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification and the features of the different embodiments or examples. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, the feature specified as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means two or more, unless otherwise explicitly specified. Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this disclosure includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the function involved. The logic and / or steps described in the flowchart or otherwise herein, for example, can be considered as a ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, instruction execution systems, apparatuses, or devices (such as computer-based systems, processor-included systems, or other systems that can fetch and execute instructions from and from such instruction execution systems, apparatuses, or devices). It should be understood that... The various parts of this disclosure can be implemented in hardware, software, firmware, or a combination thereof.In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. This program can be stored in a computer-readable storage medium. When executed, the program includes one or a combination of the steps of the method embodiments. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a disk, or an optical disk, etc. The above descriptions are merely exemplary embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope described in this disclosure, and these should all be covered within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

CLAIM 1.A cloud service access method, applied to a client, wherein the client is in communication connection with a micro-service end, the micro-service end comprises a service load balancing server, one or more backend servers and a load balancing service, the client is configured with a first private network, the micro-service end is configured with a second private network, a first terminal node of the service load balancing server and a second terminal node of a private network connection service are configured in the first private network, and the private network connection service is used to connect the first private network and the second private network; the method comprises the following steps: sending, by the first terminal node, an access request to the service load balancing server; receiving, by the first terminal node, an IP address of the second terminal node returned by the service load balancing server in response to the access request; when receiving message data, accessing, by the first terminal node, the private network connection service through the IP address, and sending, by the first terminal node, the message data to the load balancing service through the private network connection service, so that the load balancing service sends the message data to the backend server according to cloud service information and configuration information, wherein the message data carries the cloud service information, the cloud service information is used to determine a cloud service to be accessed, and the configuration information is returned by the service load balancing server to the load balancing service in response to the access request.

2. The method according to claim 1, wherein, sending, by the first terminal node, an access request to the service load balancing server, including: generating an access request in a specified manner; and sending the access request to the first terminal node, so that the first terminal node sends the access request to the service load balancing server.

3. The method according to claim 2, wherein, The client is configured with an SDK tool, and the access request is generated in a specified manner, including: generating the access request based on the SDK tool.

4. The method according to claim 1, wherein, accessing, by the first terminal node, the private network connection service through the IP address, and sending, by the first terminal node, the message data to the load balancing service through the private network connection service, including: accessing the second terminal node based on the IP address; and sending, by the first terminal node, the message data to the private network connection service through the second terminal node, so that the private network connection service sends the message data to the load balancing service.

5. A method for processing access request, applied to a micro-service side, wherein the micro-service side and a client are in communication connection, the micro-service side comprises a service load balancing server, one or more backend servers and a load balancing service, the client is configured with a first private network, the micro-service side is configured with a second private network, the first private network is configured with a first terminal node of the service load balancing server and a second terminal node of a private network connection service, and the private network connection service is used to connect the first private network and the second private network; the method comprises: in response to receiving an access request of a client, sending, by the service load balancing server, an IP address of a second terminal node to the client, and sending configuration information to the load balancing service, so that the client accesses the private network connection service through the IP address, and sends message data to the load balancing service through the private network connection service, wherein the message data carries cloud service information, the cloud service information is used to determine a cloud service to be accessed, and the configuration information is returned by the service load balancing server to the load balancing service in response to the access request; sending, by the load balancing service, the message data to the backend server according to the cloud service information and the configuration information.

6. The method according to claim 5, wherein, The configuration information is used to configure a server corresponding to a cloud service; and sending the message data to the backend server according to the cloud service information and the configuration information, including: determining a cloud service to be accessed according to the message data; determining a target IP address corresponding to the cloud service to be accessed based on the configuration information; and sending the message data to a server corresponding to the target IP address.

7. The method according to claim 6, wherein, The target IP address is determined in the IP address of the server, including: determining the target IP address randomly in the IP address of the server, or taking the IP address of the server in an idle state as the target IP address.

8. The method according to claim 7, wherein, The target IP address is determined in the IP address of the server, including: determining the target IP address randomly in the IP address of the server, or taking the IP address of the server in an idle state as the target IP address. 9.A cloud service access apparatus, applied to a client, wherein the client is in communication connection with a micro-service side, the micro-service side comprises a service load balancing server, one or more backend servers and a load balancing service, the client is configured with a first private network, the micro-service side is configured with a second private network, a first terminal node of the service load balancing server and a second terminal node of a private network connection service are configured in the first private network, and the private network connection service is used to connect the first private network and the second private network; the apparatus comprises: The request module is configured to send an access request to the service load balancing server through the first terminal node; the acquisition module is configured to acquire the IP address of the second terminal node returned by the service load balancing server in response to the access request; The access module is configured to, when receiving message data, access the private network connection service through the IP address, and send the message data to the load balancing service by using the private network connection service, so that the load balancing service sends the message data to the backend server according to cloud service information and configuration information, wherein the message data carries the cloud service information, the cloud service information is used to determine a cloud service to be accessed, and the configuration information is returned to the load balancing service by the service load balancing server in response to the access request.

10. An access request processing apparatus, applied to a micro-service end, wherein the micro-service end and a client are in communication connection, the micro-service end comprises a service load balancing server, one or more backend servers and a load balancing service, the client is configured with a first private network, the micro-service end is configured with a second private network, the first private network is configured with a first terminal node of the service load balancing server and a second terminal node of a private network connection service, and the private network connection service is used to connect the first private network and the second private network; the apparatus comprises: The control module is configured to, in response to receiving an access request of a client, send, by using the service load balancing server, an IP address of a second terminal node to the client, and send configuration information to the load balancing service, so that the client accesses the private network connection service through the IP address, and sends message data to the load balancing service by using the private network connection service, wherein the message data carries cloud service information, the cloud service information is used to determine a cloud service to be accessed, and the configuration information is returned to the load balancing service by the service load balancing server in response to the access request; the load balancing module is configured to send, by using the load balancing service, the message data to the backend server according to the cloud service information and the configuration information.

11. An electronic device comprising a memory, a processor, and a computer program stored on the memory, the processor implementing the method of any one of claims 1-8 when executing the computer program.

12. A computer-readable storage medium having a computer program stored therein, the computer program implementing the method of any one of claims 1-8 when executed by a processor. The computer program product comprises a computer program, the computer program implementing the method of any one of claims 1-8 when executed by a processor.

13. A computer program product, wherein, ​ 19

Images