Cross-resource pool access method and device, equipment, medium and program product

Abstract

The invention provides a cross-resource-pool access method and device, equipment, a medium and a program product, and the method comprises the steps: receiving an access request from a front end of a target micro-service system; forwarding the access request to a corresponding back-end micro-service deployed in the first resource pool according to a predefined routing strategy; wherein the predefined routing strategy comprises the step that the transfer service forwards a request that the front-end service comprises a nested page or the front-end service calls the rear-end service. According to the embodiment of the invention, a transfer service and a predefined routing strategy are introduced, front-end'zero perception 'and business seamless migration are realized, and a solid foundation is laid for continuous iteration of a system and large-scale expansion of a micro-service architecture.

Description

Technical Field

[0001] This disclosure relates to the field of information technology, and more specifically, to a method, apparatus, device, medium, and program product for accessing resources across a pool. Background Technology

[0002] Currently, against the backdrop of accelerated digital transformation in enterprises, large-scale AI models and their related subsystems (such as knowledge management systems) are gradually becoming important infrastructure supporting intelligent enterprise operations. To cope with the elastic demands on system resources from high-concurrency scenarios such as online training and examinations, while ensuring the service quality and continuity of core online businesses, it is necessary to build intelligent scheduling and migration capabilities across resource pools.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The purpose of this disclosure is to provide a method, apparatus, device, medium, and program product for cross-resource pool access, which at least to some extent overcomes the problem that cross-resource pool access cannot be achieved due to limitations and defects in related technologies.

[0005] According to a first aspect of the present disclosure, a method for accessing resources across resource pools is provided, comprising: Receive access requests from the front end of the target microservice system; According to the predefined routing strategy, the access request is forwarded to the corresponding backend microservice deployed in the first resource pool; The predefined routing strategy includes forwarding requests from front-end services containing nested pages or front-end services calling back-end services by the relay service.

[0006] In one exemplary embodiment of this disclosure, before receiving an access request from the front end of the target microservice system, the method further includes: The system receives access requests from the portal service, which are obtained by the portal service based on the permissions of the specific user role after the user selects a specific user role through the unified authentication portal. The access request is forwarded to the front end of the target microservice system deployed in the first resource pool, so that the front end of the target microservice system configures the service address and / or loads the user interface according to the user permissions obtained from the portal service.

[0007] In one exemplary embodiment of this disclosure, the method of configuring the service address includes: In response to the front-end service request to load the nested page, the access address of the front-end service is configured to point to the load balancer address and port of the relay service; In response to the front-end service request to call the back-end service, the target address of the call request is configured to point to the load balancer address and port of the relay service; In response to a request from one of the backend services to invoke another backend service, the target address for the invocation between the multiple backend services is configured as the actual address and port of the backend service being invoked in the first resource pool environment.

[0008] In one exemplary embodiment of this disclosure, before receiving the access request, the method further includes: Determine the original routing architecture in the user's access system; From the original routing architecture, configurable access routes and network routes that need to be applied for are separated; Based on the partitioned access routes and / or network routes, a relay service is built; In the relay service, configure routing information for all microservice systems leading to the first resource pool; The constructed relay service is deployed in the second resource pool; Based on the deployed relay service, the network path between the second resource pool and the first resource pool is established.

[0009] In one exemplary embodiment of this disclosure, before receiving the access request, the method further includes: Obtain the modified routing information. The modified routing information includes at least one of the following: routes between front-end services, routes to back-end services accessed by the front-end, and routes between back-end services. Configure the predefined routing policy based on the modified route.

[0010] In one exemplary embodiment of this disclosure, obtaining the modified routing information includes: Determine the existing routing information of the target microservice system, including routes for communication between front-end services, routes for front-end services to access back-end services, and routes for communication between back-end services. Based on the existing routing information, the routes for communication between the front-end services and the routes for the front-end services to access the back-end services are modified so that the modified routes point to the relay service. The modified routing information is synchronized to the relay service so that the relay service can forward access requests to the corresponding service deployed on the first resource pool based on the routing information.

[0011] In one exemplary embodiment of this disclosure, forwarding the access request to the corresponding backend microservice deployed in the first resource pool according to a predefined routing strategy includes: The access request is parsed to obtain a parsing result, which includes a Uniform Resource Identifier and / or request header information; Based on the parsing results, the network address of the target backend microservice in the first resource pool is determined by matching it with the predefined routing strategy. The access request is repackaged and forwarded to the network address corresponding to the target backend microservice.

[0012] In one exemplary embodiment of this disclosure, the access request is configured to be routed from a portal service through a load balancer, which performs traffic scheduling on multiple relay service instances.

[0013] In one exemplary embodiment of this disclosure, the specific user role includes a training user role bound to the permission to access the relay service.

[0014] According to a second aspect of the present disclosure, a cross-resource pool access device is provided, comprising: The receiving module is configured to receive access requests from the front end of the target microservice system; The forwarding module is configured to forward the access request to the corresponding backend microservice deployed in the first resource pool according to a predefined routing strategy. The predefined routing strategy includes forwarding requests from front-end services containing nested pages or front-end services calling back-end services by the relay service.

[0015] According to a third aspect of this disclosure, an electronic device is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to perform a cross-resource pool access method as described in any one of the preceding claims based on instructions stored in the memory.

[0016] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided having a program stored thereon that, when executed by a processor, implements the cross-resource pool access method as described in any of the preceding claims.

[0017] According to a fifth aspect of this disclosure, a computer program product is provided, which, when executed by a processor, implements the cross-resource pool access method as described in any of the preceding claims.

[0018] This embodiment of the disclosure achieves seamless business migration with "zero awareness" from the front end by introducing a relay service and predefined routing policies. The front-end application requires no modification; it continues to send requests to the original target address (still in resource pool B or the unified entry point) as usual. All routing and forwarding logic is handled in the background by the relay service, making the cross-resource pool migration of the knowledge management subsystem completely transparent to users and the front-end application, achieving true "business-aware migration" and greatly improving operational agility and user experience continuity. Under the mediation of the relay service, the front-end and back-end services are decoupled. Based on this, neither needs to know the other's specific network location. Furthermore, the expansion, migration, and replacement of back-end services can all be completed at the relay service layer by updating the routing policy without disturbing the front end, laying a solid foundation for continuous system iteration and the scalable expansion of the microservice architecture.

[0019] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0021] Figure 1 A schematic diagram of an exemplary system architecture for which cross-resource pool access schemes can be applied according to embodiments of the present disclosure is shown.

[0022] Figure 2 This is a flowchart of a cross-resource pool access scheme in the prior art.

[0023] Figure 3 This is a flowchart of a cross-resource pool access method in an exemplary embodiment of this disclosure.

[0024] Figure 4 This is a flowchart of another cross-resource pool access method in an exemplary embodiment of this disclosure.

[0025] Figure 5 This is a flowchart of another cross-resource pool access method in an exemplary embodiment of this disclosure.

[0026] Figure 6 This is a flowchart of another cross-resource pool access method in an exemplary embodiment of this disclosure.

[0027] Figure 7This is a block diagram of an access device across resource pools according to an exemplary embodiment of this disclosure.

[0028] Figure 8 This is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0029] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0030] Furthermore, the accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0031] As enterprises deepen their digital transformation, large-scale AI models and their subsystems (such as knowledge management systems) have become core infrastructure. Company A's large-scale network model is deployed in resource pool B to provide intelligent services to internal and external users.

[0032] When facing high-concurrency special events such as online training and examinations, in order to ensure that the main business is not affected, the knowledge management subsystem needs to be temporarily migrated to resource pool A. However, this migration faces severe technical challenges, making traditional solutions unsuitable: First, network isolation is a fundamental obstacle. Resource pools A and B are not connected to each other, hindering data synchronization and service calls; at the same time, user clients have no direct network path to resource pool A, and authorization on a user-by-user basis is extremely inefficient and cannot meet the agility requirements of temporary activities.

[0033] Secondly, the requirements for business continuity are stringent. The main business must remain uninterrupted, and the user experience must be strictly consistent. Any changes to the login or interaction process due to architectural adjustments are unacceptable.

[0034] Finally, strict security and compliance restrictions apply. Cross-resource pool access must inherit the existing 4A authentication and permission system, while data transmission must meet high-level security audits to prevent leaks and attacks.

[0035] Existing traditional technologies such as VPN connectivity, DNS switching, or client-side modifications suffer from inherent drawbacks, including long deployment cycles, complex maintenance, and potential disruptions to the user experience. These limitations fail to meet the urgent needs of enterprise applications for high availability, high security, and seamless migration. Therefore, a smart and transparent new solution is urgently needed to achieve a smooth, seamless user transition and continuous, stable business operation without requiring large-scale network modifications.

[0036] Figure 1 A schematic diagram of an exemplary system architecture for which cross-resource pool access schemes can be applied according to embodiments of the present disclosure is shown.

[0037] like Figure 1 As shown, system architecture 100 may include one or more of terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0038] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, there can be any number of terminal devices, networks, and servers. For example, server 105 could be a server cluster composed of multiple servers.

[0039] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Terminal devices 101, 102, and 103 can be various electronic devices with displays, including but not limited to smartphones, tablets, laptops, and desktop computers, etc.

[0040] In some embodiments, the cross-resource pool access method provided in this disclosure is generally executed by server 105, and correspondingly, the cross-resource pool access device is generally located in terminal device 103 (or terminal device 101 or 102). In other embodiments, some terminals may have similar functions to the server device to execute this method.

[0041] In one exemplary embodiment of this disclosure, such as Figure 2 As shown, the original access method for process 200 includes the following steps: 1. Select the Qiming Network Big Model System through the Group's Yitong client, complete the portal redirection to the Network Big Model System through the 4A account, and select the knowledge management training user role, or enter the Network Big Model System through the Group's 4A client and select the knowledge management training user role.

[0042] 2. The portal reads the configuration and redirects to the knowledge management service via SLB.

[0043] 3. Knowledge management front-end, with token access to the portal to obtain permissions.

[0044] 4. The portal returns user permissions for the knowledge management system.

[0045] 5. The knowledge management front end loads the corresponding pages and menus based on user permissions.

[0046] 6. Knowledge management front-end, loading result data.

[0047] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0048] Figure 3 This is a flowchart of a cross-resource pool access method in an exemplary embodiment of this disclosure.

[0049] refer to Figure 3 Methods for accessing resources across pools can include: Step S302: Receive an access request from the front end of the target microservice system; Step S304: According to the predefined routing strategy, the access request is forwarded to the corresponding backend microservice deployed in the first resource pool; The predefined routing strategy includes forwarding requests from front-end services containing nested pages or front-end services calling back-end services by the relay service.

[0050] In this embodiment of the disclosure, by introducing a relay service and a predefined routing strategy, the front-end achieves "zero-awareness" and seamless business migration. The front-end application does not need to be modified at all; it still sends requests to the original target address (still in resource pool B or the unified entry point) as usual.

[0051] Furthermore, all routing and forwarding logic is handled in the background by the relay service. This makes the cross-resource pool migration of the knowledge management subsystem completely transparent to users and front-end applications, achieving true "business-aware migration" and greatly improving operational agility and user experience continuity. Under the mediation of the relay service, front-end and back-end services are decoupled.

[0052] Furthermore, neither party needs to know the other's specific network location. The expansion, migration, and replacement of backend services can all be completed in the transit service layer by updating the routing strategy, without disturbing the frontend. This lays a solid foundation for the continuous iteration of the system and the large-scale expansion of the microservice architecture.

[0053] In one exemplary embodiment of this disclosure, a user clicks the "Online Training" entry on the client side. The request generated by this click is sent to a relay service. The relay service, based on a pre-defined policy, identifies this as a nested page request from a knowledge management subsystem and forwards it to the training system frontend deployed in resource pool A (i.e., the aforementioned first resource pool). After the frontend loads, its internal requests to call backend APIs (such as retrieving a list of test papers) also target the relay service, which then forwards them again to the corresponding backend microservice in resource pool A.

[0054] The following section details each step of the method for accessing resources across pools.

[0055] In one exemplary embodiment of this disclosure, before receiving an access request from the front end of the target microservice system, the method further includes: The system receives access requests from the portal service, which are obtained by the portal service based on the permissions of the specific user role after the user selects a specific user role through the unified authentication portal. The access request is forwarded to the front end of the target microservice system deployed in the first resource pool, so that the front end of the target microservice system configures the service address and / or loads the user interface according to the user permissions obtained from the portal service.

[0056] In this embodiment of the disclosure, by elevating the initiator of the access request from a regular front-end to a unified authentication portal (4A system), the legitimacy of the request source and the certainty of the user role are ensured. The address and UI configuration of the front-end service can be dynamically obtained from the portal according to the user role, which makes it possible to push different functions or access different resource pools to different roles (such as ordinary employees and administrators), greatly improving the flexibility and personalization of the system.

[0057] In one exemplary embodiment of this disclosure, a user logs into the group's unified portal and selects the "Training Examinee" role from the role menu. Based on this role, the portal service routes the user to the front-end address of the knowledge management system (this address has been pre-configured to point to the relay service). At the same time, the portal also returns the customized service address and UI configuration information corresponding to this role to the front-end, which then loads a user interface specifically designed for the exam.

[0058] In one exemplary embodiment of this disclosure, the method of configuring the service address includes: In response to the front-end service request to load the nested page, the access address of the front-end service is configured to point to the load balancer address and port of the relay service; In response to the front-end service request to call the back-end service, the target address of the call request is configured to point to the load balancer address and port of the relay service; In response to a request from one of the backend services to invoke another backend service, the target address for the invocation between the multiple backend services is configured as the actual address and port of the backend service being invoked in the first resource pool environment.

[0059] This disclosure provides a clear configuration guide for system transformation by using three different address configuration methods in different scenarios. This ensures that all communication from the user / frontend to the backend goes through a relay service, while calls between backends are efficiently completed within the resource pool. This avoids configuration confusion and omissions, ensures the clarity and maintainability of the architecture, and direct calls between backend services avoid unnecessary network detours, ensuring low latency and high performance of internal system communication.

[0060] In one exemplary embodiment of this disclosure, the access address of the training system front-end corresponding to the nested page is configured as https: / / gateway.ct.com / training-app.

[0061] In one exemplary embodiment of this disclosure, the API call is a front-end call to the "Submit Exam Paper" API, with the target address being https: / / gateway.ct.com / api / exam / submit.

[0062] In one exemplary embodiment of this disclosure, in the case of inter-service calls, if the "Examination Service" needs to call the "User Information Service" within resource pool A, it directly uses the intranet address http: / / user-service.internal:8080 / info.

[0063] In one exemplary embodiment of this disclosure, before receiving the access request, the method further includes: Determine the original routing architecture in the user's access system; From the original routing architecture, configurable access routes and network routes that need to be applied for are separated; Based on the partitioned access routes and / or network routes, a relay service is built; In the relay service, configure routing information for all microservice systems leading to the first resource pool; The constructed relay service is deployed in the second resource pool; Based on the deployed relay service, the network path between the second resource pool and the first resource pool is established.

[0064] This disclosure reduces implementation difficulty and risk by breaking down the complex migration project into a standardized process of "analysis-division-construction-configuration-deployment-connection". Furthermore, by clearly defining "configurable access routes" and "network routes that need to be applied for", the migration work can focus only on application layer route configuration without large-scale modification of underlying network security policies (such as firewall rules), thereby improving security and implementation efficiency.

[0065] In one exemplary embodiment of this disclosure, all services of the original system reside in resource pool B. The front end directly accesses the back end via an intranet domain name. "Front end accessing knowledge management back end" is a configurable access route. "Network interconnection from resource pool B (i.e., the second resource pool) to resource pool A" is a network route that needs to be applied for and enabled. A relay service (such as based on Nginx or Spring Cloud Gateway) is built in resource pool B, and all routing rules pointing to the knowledge management service in resource pool A are configured. The developers enable a secure access policy from the relay service of resource pool B to a specific network segment of resource pool A.

[0066] In one exemplary embodiment of this disclosure, before receiving the access request, the method further includes: Obtain the modified routing information. The modified routing information includes at least one of the following: routes between front-end services, routes to back-end services accessed by the front-end, and routes between back-end services. Configure the predefined routing policy based on the modified route.

[0067] This disclosure embodiment, through the modified routing and configuration of the predefined routing policy, provides a specific solution for evolving from an existing monolithic or tightly coupled architecture to a flexible cross-resource pool architecture. It emphasizes the "synchronization" of the modified routing information to the relay service, which is a key step to ensure that traffic is forwarded correctly and avoids service unavailability caused by information asynchrony.

[0068] In one exemplary embodiment of this disclosure, the frontend accesses the knowledge service directly via http: / / knowledge-service-b.internal / api / data. Alternatively, the frontend can access https: / / gateway.ct.com / knowledge / api / data. The operations and maintenance personnel will then configure this new routing rule (which will link / knowledge / ...) Traffic is forwarded to the knowledge-service-a.internal route table configured in the relay service.

[0069] In one exemplary embodiment of this disclosure, obtaining the modified routing information includes: Determine the existing routing information of the target microservice system, including routes for communication between front-end services, routes for front-end services to access back-end services, and routes for communication between back-end services. Based on the existing routing information, the routes for communication between the front-end services and the routes for the front-end services to access the back-end services are modified so that the modified routes point to the relay service. The modified routing information is synchronized to the relay service so that the relay service can forward access requests to the corresponding service deployed on the first resource pool based on the routing information.

[0070] In one exemplary embodiment of this disclosure, forwarding the access request to the corresponding backend microservice deployed in the first resource pool according to a predefined routing strategy includes: The access request is parsed to obtain a parsing result, which includes a Uniform Resource Identifier and / or request header information; Based on the parsing results, the network address of the target backend microservice in the first resource pool is determined by matching it with the predefined routing strategy. The access request is repackaged and forwarded to the network address corresponding to the target backend microservice.

[0071] In this embodiment of the disclosure, by parsing the request content (URI, Header) for matching, the routing decision is no longer limited to static configuration. It can distribute traffic to the most suitable backend instance based on dynamic factors such as request content and user information.

[0072] In one exemplary embodiment of this disclosure, a portion of user traffic can be directed to a new test version based on the "grayscale label" in the header, thereby achieving grayscale release.

[0073] In one exemplary embodiment of this disclosure, the relay service receives a request, resolves the URI to / api / v1 / exam / paper and the header to contain User-Role:tester. According to the routing policy, the request for User-Role:tester should be routed to the "canary environment" of resource pool A, and the request is forwarded to http: / / exam-service-canary.pool-a / internal / api / v1 / paper.

[0074] In one exemplary embodiment of this disclosure, the access request is configured to be routed from a portal service through a load balancer, which performs traffic scheduling on multiple relay service instances.

[0075] This embodiment of the disclosure avoids single points of failure by scheduling multiple relay service instances through a load balancer, and can scale according to the level of access pressure, easily handling high-concurrency scenarios such as "network-wide training".

[0076] In one exemplary embodiment of this disclosure, an F5 load balancer is placed in front of the portal, and three relay service instances are deployed behind it. Requests to the portal are evenly distributed across these three instances, ensuring uninterrupted service even if one instance fails.

[0077] In one exemplary embodiment of this disclosure, the specific user role includes a training user role bound to the permission to access the relay service.

[0078] This embodiment of the disclosure achieves coarse-grained access control at a unified authentication level by directly linking access permissions of the resource pool to business roles (such as "training users"), resulting in higher security and more convenient management.

[0079] In one exemplary embodiment of this disclosure, the portal only routes a user's request to the knowledge management subsystem if the user selects either the "Training Candidate" or "Training Administrator" role on the portal. Users who select other roles will not be able to see or access this entry point.

[0080] In one exemplary embodiment of this disclosure, such as Figure 4 As shown, the cross-resource pool access process 400 disclosed herein includes the following steps: 1. Users can select the Qiming Network Big Model System through the Group's Yitong or 4A client, and complete the redirection to the portal service of the Network Big Model System through their 4A account, and select the knowledge management training user role.

[0081] 2. The portal service reads the permission configuration of the logged-in user. For users with knowledge management permissions, they are redirected to the relay service through the pre-configured SLB service of resource pool B.

[0082] 3. The relay service will forward the request to the knowledge management homepage of resource pool A.

[0083] 4. Knowledge management front-end service: Access the portal service based on the token in the link to obtain the set of permissions of the currently logged-in user in the knowledge management system.

[0084] 5. The portal service returns the set of knowledge management system permissions that the currently logged-in user has pre-configured in the portal service.

[0085] 6. The knowledge management front-end service loads the corresponding page and menu based on user permissions. Since the knowledge management system uses a microservice architecture, three scenarios need to be handled separately: If the front-end service contains nested pages, then the front-end service configuration should point to the SLB address and port of the relay service; When the frontend calls the backend, the frontend service configuration points to the SLB address and port of the relay service. Backend calls backend: The backend service configuration points to the address and port of the backend service in resource pool A environment.

[0086] Step 7: The relay service parses and forwards the request to the corresponding microservice IP and port in resource pool A's knowledge management system.

[0087] Step 8: The knowledge management front-end service loads the result data and presents it to the user.

[0088] In one exemplary embodiment of this disclosure, such as Figure 5 As shown, the cross-resource pool access process 500 disclosed herein includes the following steps: 1. Take stock of the overall routes currently used by user clients to access the system; 2. Define routes that are transparent to user clients when accessing the system, and distinguish between routes that can be configured by the user and routes that require a network access policy work order; 3. Configure the routing policy from the transit service to the first resource pool (resource pool A) of the new resource pool; 4. For parts that require network connectivity, minimize the scope as much as possible, separate them from systems directly accessed by users, extract them into a separate relay service, and ensure that the deployment and testing process is transparent and imperceptible to users. 5. Determine which resource pool the relay service will be deployed in, and apply for and test network port connectivity; 6. Build a relay service and configure all access routes to the knowledge management service deployed on the first resource pool (resource pool A) of the new resource pool in the relay service; 7. Deploy the completed relay service to this resource pool; 8. Configure a new permission in the system portal that enables access routing to the relay service, and grant this permission to the training user; 9. Simulate a training user accessing the portal, selecting a knowledge management training role, and completing the access to the knowledge management service homepage.

[0089] In one exemplary embodiment of this disclosure, such as Figure 6 As shown, the cross-resource pool access process 600 disclosed herein includes the following steps: 1. Conduct an inventory of the overall routing of all front-end and back-end services for knowledge management; 2. Define the routes for communication between front-end services, the routes for communication between front-end services and back-end services, and the routes for communication between back-end services. 3. Modify the routing for communication between various front-end services and the routing for access to various back-end services from the front-end; 4. Synchronize the results of the modified routing to the relay service; 5. Rebuild all front-end and back-end services and deploy them on the first resource pool (resource pool A) of the new resource pool; 6. Simulate a training user accessing the portal, selecting a knowledge management training role, and completing access to all functions of the knowledge management service.

[0090] In one exemplary embodiment of this disclosure, accessing the knowledge management training system deployed in resource pool A from the homepage of the Qiming Big Model in online resource pool B involves the following specific implementation steps: 1. In resource pool A, the access port of the knowledge management system should be bidirectionally connected to the address and port of the Qiming Big Model permission interface in resource pool B. The connection from resource pool B to resource pool A can be configured instantly via the Tianyi Cloud platform; the reverse connection requires submitting a network policy activation ticket to the cloud company.

[0091] 2. Build and deploy a relay service in resource pool B, such as SLBR:PORTR / URIR, to receive requests and forward them to the address and port IPKG:PORTKG of the knowledge management front-end service in resource pool A.

[0092] 3. Add training permission to the Qiming large model in resource pool B, and point the link of this permission to the address and port of the relay service SLBR:PORTR / URIR.

[0093] 4. Simulate a user logging in from the client and accessing the Qiming Network large model, selecting the knowledge management training role, and successfully being redirected to the knowledge management service homepage.

[0094] 5. Organize the knowledge management front-end service deployed in resource pool A. All resource links pointing to the back-end address port need to be re-labeled. For example, the original access link IP1:PORT1 / URI1 should be changed to IP1:PORT1 / LABEL1 / URI1. The set of these links is recorded as A. The resource links nested between front-end pages also need to be recorded without modification. The set of these links is recorded as B.

[0095] 6. Replace the original configuration of the knowledge management front-end of resource pool A, and add A and B to the relay service configuration of resource pool B.

[0096] 7. Based on the new configuration, rebuild the front-end and back-end services of resource pool A, and ensure that the service test cases within resource pool A pass.

[0097] 8. Based on the new configuration, rebuild the relay service of resource pool B and complete the test cases from the portal to the relay and then to the resource pool A service.

[0098] 9. Simulate a user logging in from the client, accessing the Qiming Network large model, selecting a knowledge management training role, successfully redirecting to the knowledge management service, and completing all functional test cases.

[0099] Corresponding to the above method embodiments, this disclosure also provides a cross-resource pool access device, which can be used to execute the above method embodiments.

[0100] Figure 7 This is a block diagram of an access device across resource pools according to an exemplary embodiment of this disclosure.

[0101] refer to Figure 7 The cross-resource pool access device 700 may include: The receiving module 702 is configured to receive access requests from the front end of the target microservice system; The forwarding module 704 is configured to forward the access request to the corresponding backend microservice deployed in the first resource pool according to a predefined routing strategy. The predefined routing strategy includes forwarding requests from front-end services containing nested pages or front-end services calling back-end services by the relay service.

[0102] In one exemplary embodiment of this disclosure, the cross-resource pool access device 700 is further configured to: The system receives access requests from the portal service, which are obtained by the portal service based on the permissions of the specific user role after the user selects a specific user role through the unified authentication portal. The access request is forwarded to the front end of the target microservice system deployed in the first resource pool, so that the front end of the target microservice system configures the service address and / or loads the user interface according to the user permissions obtained from the portal service.

[0103] In one exemplary embodiment of this disclosure, the cross-resource pool access device 700 is further configured to: In response to the front-end service request to load the nested page, the access address of the front-end service is configured to point to the load balancer address and port of the relay service; In response to the front-end service request to call the back-end service, the target address of the call request is configured to point to the load balancer address and port of the relay service; In response to a request from one of the backend services to invoke another backend service, the target address for the invocation between the multiple backend services is configured as the actual address and port of the backend service being invoked in the first resource pool environment.

[0104] In one exemplary embodiment of this disclosure, the cross-resource pool access device 700 is further configured to: Determine the original routing architecture in the user's access system; From the original routing architecture, configurable access routes and network routes that need to be applied for are separated; Based on the partitioned access routes and / or network routes, a relay service is built; In the relay service, configure routing information for all microservice systems leading to the first resource pool; The constructed relay service is deployed in the second resource pool; Based on the deployed relay service, the network path between the second resource pool and the first resource pool is established.

[0105] In one exemplary embodiment of this disclosure, the cross-resource pool access device 700 is further configured to: Obtain the modified routing information. The modified routing information includes at least one of the following: routes between front-end services, routes to back-end services accessed by the front-end, and routes between back-end services. Configure the predefined routing policy based on the modified route.

[0106] In one exemplary embodiment of this disclosure, the cross-resource pool access device 700 is further configured to: Determine the existing routing information of the target microservice system, including routes for communication between front-end services, routes for front-end services to access back-end services, and routes for communication between back-end services. Based on the existing routing information, the routes for communication between the front-end services and the routes for the front-end services to access the back-end services are modified so that the modified routes point to the relay service. The modified routing information is synchronized to the relay service so that the relay service can forward access requests to the corresponding service deployed on the first resource pool based on the routing information.

[0107] In one exemplary embodiment of this disclosure, the forwarding module 704 is further configured to: The access request is parsed to obtain a parsing result, which includes a Uniform Resource Identifier and / or request header information; Based on the parsing results, the network address of the target backend microservice in the first resource pool is determined by matching it with the predefined routing strategy. The access request is repackaged and forwarded to the network address corresponding to the target backend microservice.

[0108] In one exemplary embodiment of this disclosure, the access request is configured to be routed from a portal service through a load balancer, which performs traffic scheduling on multiple relay service instances.

[0109] In one exemplary embodiment of this disclosure, the specific user role includes a training user role bound to the permission to access the relay service.

[0110] Since the functions of the device 700 have been described in detail in their respective method embodiments, they will not be repeated here.

[0111] It should be noted that although the description above mentions the responsiveness of the device for performing actions to modules or units, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0112] In an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0113] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0114] The following reference Figure 8 To describe an electronic device 800 according to such an embodiment of the present disclosure. Figure 8 The electronic device 800 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0115] like Figure 8 As shown, the electronic device 800 is manifested in the form of a general-purpose computing device. The components of the electronic device 800 may include, but are not limited to: at least one processing unit 810, at least one storage unit 820, and a bus 830 connecting different system components (including storage unit 820 and processing unit 810).

[0116] The storage unit stores program code that can be executed by the processing unit 810, causing the processing unit 810 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure. For example, the processing unit 810 can perform the method shown in the embodiments of this disclosure.

[0117] Storage unit 820 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 8201 and / or cache memory 8202, and may further include a read-only memory (ROM) 8203.

[0118] The storage unit 820 may also include a program / utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0119] Bus 830 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0120] Electronic device 800 can also communicate with one or more external devices 840 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 800, and / or with any device that enables electronic device 800 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 850. Furthermore, electronic device 800 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 860. As shown, network adapter 860 communicates with other modules of electronic device 800 via bus 830. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0121] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, portable hard drive, etc.) or on a network, including responding to instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the method according to the embodiments of this disclosure.

[0122] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible implementations, various aspects of this disclosure may also be implemented as a program product including program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of this disclosure described in the "Exemplary Methods" section above.

[0123] The program product for implementing the above-described method according to embodiments of this disclosure may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of this disclosure is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0124] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0125] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0126] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0127] Program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0128] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this disclosure and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0129] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and concept of this disclosure are indicated by the claims.

Claims

1. A cross-resource pool access method, characterized in that, Comprising: receiving an access request from a front-end of a target micro-service system; forwarding the access request to a corresponding back-end micro-service deployed in the first resource pool according to a predefined routing strategy; wherein the predefined routing strategy comprises forwarding, by the relay service, a request for which a front-end service contains a nested page or the front-end service calls a back-end service.

2. The cross-resource pool access method of claim 1, wherein, Before receiving the access request from the front-end of the target micro-service system, further comprising: receiving an access request from a portal service, the access request being obtained by the portal service based on a permission of a specific user role after a user end selects the specific user role through a unified authentication portal; forwarding the access request to a front-end of a target micro-service system deployed in the first resource pool, so that the front-end of the target micro-service system configures a service address according to a user permission obtained from the portal service and / or loads a user interface.

3. The cross-resource pool access method of claim 2, wherein, The manner of configuring the service address comprises: in response to the front-end service requesting to load a nested page, configuring an access address of the front-end service to point to a load balancer address and port of the relay service; in response to the front-end service requesting to call a back-end service, configuring a target address of the calling request to point to the load balancer address and port of the relay service; in response to one of the back-end services calling another back-end service, configuring target addresses of calls between a plurality of the back-end services to actual addresses and ports of the called back-end services in the first resource pool environment.

4. The cross-resource pool access method of claim 1, wherein, Before receiving the access request, further comprising: determining an original routing architecture in the access system of the user end; dividing, from the original routing architecture, a configurable access route and a network route to be applied for opening; based on the divided access route and / or network route, constructing a relay service; in the relay service, configuring routing information to all micro-service systems in the first resource pool; deploying the constructed relay service in a second resource pool; based on the deployed relay service, opening a network path between the second resource pool and the first resource pool.

5. The cross-resource pool access method of claim 1, wherein, Before receiving the access request, further comprising: obtaining the modified routing information, the modified routing information comprises at least one of a routing between front-end services, a routing of a back-end service accessed by a front-end, and a routing between back-end services; based on the modified routing, configuring the predefined routing strategy.

6. The cross-resource pool access method of claim 5, wherein, Obtaining the modified routing information comprises: determining existing routing information of a target micro-service system, the existing routing information comprising a routing between front-end services, a routing of a back-end service accessed by a front-end, and a routing between back-end services; based on the existing routing information, modifying the routing between the front-end services and the routing of the back-end service accessed by the front-end, so that the modified routing points to the relay service; synchronizing the modified routing information to the relay service, so that the relay service can forward an access request to a corresponding service deployed on the first resource pool according to the routing information.

7. The cross-resource pool access method of claim 1, wherein, forwarding the access request to a corresponding backend microservice deployed in the first resource pool according to a predefined routing policy comprises: parsing the access request to obtain a parsing result, the parsing result comprising a uniform resource identifier and / or request header information; determining a network address of a target backend microservice in the first resource pool according to the predefined routing policy and the parsing result; re-encapsulating and forwarding the access request to the network address corresponding to the target backend microservice.

8. The cross-resource-pool access method of claim 2, wherein the access request is configured to be routed by a portal service through a load balancer that schedules traffic to a plurality of relay service instances.

9. The cross-resource-pool access method of claim 2, wherein the specific user role comprises a training user role bound to an access permission of the relay service. comprising: a receiving module configured to receive an access request from a front end of the target microservice system; 10. An apparatus for accessing across a resource pool, the apparatus comprising: a forwarding module configured to forward the access request to a corresponding backend microservice deployed in the first resource pool according to a predefined routing policy; wherein the predefined routing policy comprises forwarding, by the relay service, a request containing a nested page of a front end service or a call to a backend service by the front end service. comprising: a memory; 11. An electronic device, comprising: and a processor coupled to the memory, the processor configured to execute a cross-resource-pool access method as claimed in any one of claims 1-9 based on instructions stored in the memory.

12. A computer-readable storage medium having stored thereon a program, the program being executed by a processor to implement a cross-resource-pool access method as claimed in any one of claims 1-9. comprising a computer program, the computer program being executed by a processor to implement a cross-resource-pool access method as claimed in any one of claims 1-9. ​ 13. A computer program product, characterised in that ​

Images