CN114244654B

CN114244654B - URL forwarding method, device, equipment and computer storage medium

Info

Publication number: CN114244654B
Application number: CN202111561398.2A
Authority: CN
Inventors: 陈沛
Original assignee: Ping An Property and Casualty Insurance Company of China Ltd
Current assignee: Ping An Property and Casualty Insurance Company of China Ltd
Priority date: 2021-12-20
Filing date: 2021-12-20
Publication date: 2023-09-26
Anticipated expiration: 2041-12-20
Also published as: CN114244654A

Abstract

The application provides a forwarding method, a forwarding device, forwarding equipment and a computer storage medium of a URL (uniform resource locator), wherein the method is applied to a monomer architecture system migrated to a micro-service architecture system, and comprises the following steps: receiving a first URL; judging whether the service corresponding to the first URL is a micro-service or not based on a first URL mapping table; the first URL mapping table comprises a mapping relation between a second URL of a micro service interface and a third URL of the micro service interface, wherein the second URL is the URL of the micro service interface in a micro service architecture system, and the third URL is the URL of the micro service interface in a single architecture system; converting the first URL into a second URL of a target micro-service interface under the condition that the service corresponding to the first URL is micro-service; transmitting a second URL of the target micro-service interface to a second gateway; the second gateway is a gateway of the micro-service architecture system, and the second URL is used for the second gateway to call the target micro-service interface.

Description

URL forwarding method, device, equipment and computer storage medium

Technical Field

The present application relates to the field of forwarding URLs, and in particular, to a method, an apparatus, a device, and a computer storage medium for forwarding URLs.

Background

The single architecture system is an integral architecture system, the integral system uses a unified technical stack, and the naming habit of each developer on the unified resource locator (Uniform Resource Locator, URL) of the service interface in the single architecture system is different, so that the URL naming of each service interface in the single architecture system is irregular. The single architecture system can be rapidly developed and used in the early stage of projects, but with the increase of the business complexity and the business code quantity of the system, the system becomes more and more bulky, the coupling degree becomes higher and higher, and the process of upgrading the system and modifying the system into micro-services is faced at the moment.

The micro-service is to split the service coupled in the originally complex monomer architecture system into a plurality of independent small-sized services, each service maintains its own business logic, data processing and deployment, the services communicate with each other through a simple communication protocol (such as a restful API), each micro-service can be written in different languages, and the URL of the micro-service interface is generally regular, so that the service name is a unified prefix. By decoupling the coupled services in the single architecture system and splitting the services into independent micro services, the overall performance of the system can be improved, and the system has better expansibility.

In the process of transformation, if the front end does not want to transform the URL of the service interface or the workload of transforming the URL at the front end is too large, the problem that the URL in the monomer architecture system cannot be mapped to the URL in the micro service architecture system exists.

Therefore, how to realize the perfect transition of the new gateway layer and the old gateway layer in the transformation process of the single architecture system, avoid that the interfaces or the new codes in the transformation process cannot take effect in time, dynamically modify the route information, update the interfaces with problems of route or offline at any time, avoid the generation of dirty data, and are the increasingly focused problems of technicians.

Disclosure of Invention

The embodiment of the application provides a forwarding method, a forwarding device, forwarding equipment and a computer storage medium for a URL (uniform resource locator), which solve the problem that a micro service interface cannot be accessed/called and therefore cannot be used because the URL in a single architecture system is used for accessing the micro service interface in the process of upgrading and modifying the single architecture system into the micro service architecture system.

In a first aspect, an embodiment of the present application provides a method for forwarding a URL, including: receiving a first URL; judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table; the first URL mapping table comprises a mapping relation between a second URL of the micro service interface and a third URL of the micro service interface, wherein the second URL is the URL of the micro service interface in the micro service architecture system, and the third URL is the URL of the micro service interface in the single architecture system; under the condition that the service corresponding to the first URL is the micro-service, converting the first URL into a second URL of a target micro-service interface; transmitting a second URL of the target micro-service interface to a second gateway; the second gateway is a gateway of the micro service architecture system, and the second URL is used for the second gateway to call the target micro service interface.

In the above embodiment, after the single architecture system receives the first URL, in the case that the URL is determined to be the URL in the single architecture system, the gateway of the single architecture system determines, according to the stored first URL mapping table, whether the service interface corresponding to the received URL is an interface modified into the micro service. Under the condition that the interface corresponding to the URL received by the gateway is the micro-service interface which is transformed, the gateway of the single architecture system can convert the URL received by the gateway of the single architecture system into the URL of the corresponding micro-service interface based on the first URL mapping relation table and forward the converted URL to the gateway of the micro-service architecture system, so that the gateway of the micro-service architecture system can access/call the corresponding micro-service interface based on the converted URL, a user can call the corresponding service, the smooth transition of a gateway layer is realized in the process of transforming the single architecture system into the micro-service architecture system, and the problem that the micro-service interface cannot be accessed/called by using the URL in the single architecture system in the process of transforming the single architecture system into the micro-service architecture system is solved, and thus the micro-service cannot be used is solved.

In one possible implementation, before receiving the first URL, the method further includes splitting a portion of services in the monolithic architecture system into a plurality of micro-services according to the service type; configuring a second URL of the plurality of micro-service interfaces; configuring a first gateway, wherein the first gateway is a gateway of the single architecture system, and the configured first gateway is used for judging whether the service corresponding to the first URL is a target micro-service or not; and configuring a second gateway, wherein the second gateway is used for calling the target micro-service interface based on the second URL. In this way, after receiving the first URL, the first gateway may convert the first URL into the URL in the corresponding micro service architecture system and send the converted URL to the second gateway, so as to implement the call of the second gateway to the micro service interface corresponding to the first URL, and further implement that in the process of transforming the single architecture system into the micro service architecture system, the user may access the service split into the micro service through the URL of the service interface in the original single architecture system.

In one possible implementation, configuring the first gateway includes: establishing a first dynamic router; registering a first Zuul configuration component and a first route locator in a first dynamic router; the first Zuul configuration component is used for storing a first URL mapping table, and the first route locator is used for judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table; and configuring a first service monitoring component in the first dynamic router, wherein the first service monitoring component is used for periodically calling the second gateway through the http interface, acquiring a second URL of the micro service, and writing the corresponding relation between the second URL of the micro service interface and a third URL of the micro service interface into a first URL mapping table. In the above embodiment, the first Zuul configuration component and the first route locator are registered in the first dynamic router, so that the first dynamic router may determine whether the service corresponding to the first URL received by the first dynamic router is a service or a micro-service in the monomer architecture system based on the first Zuul configuration component and the first route locator, and convert the first URL into the second URL according to the determination result and send the second URL to the second gateway, or call a corresponding service interface in the monomer architecture system based on the first URL.

In one possible implementation manner, configuring the first gateway further includes: and configuring a right management component in the first dynamic router, wherein the right management component is used for carrying out right management of service interface access on the network equipment of the first URL transmitting end. Therefore, the first dynamic router can reject the network equipment without access authority to access the service interface, and avoid the data leakage of the service or the micro-service in the monomer architecture system, thereby causing the information security problem.

In one possible implementation, configuring the second gateway includes: establishing a second dynamic router; registering a second Zuul configuration component and a second route locator in a second dynamic router; the second Zuul configuration component comprises a second URL mapping table, the second URL mapping table comprises a mapping relation between a second URL of the micro service interface and identification information corresponding to the micro service interface, or the second URL mapping table comprises a mapping relation between the second URL of the micro service interface, a third URL of the micro service interface and identification information corresponding to the micro service interface, and the second routing locator is used for calling the target micro service interface based on the second URL mapping table and the second URL; and configuring a second service monitoring component in the second dynamic router, wherein the second service monitoring component is used for monitoring a second URL generation state of the micro-service, and dynamically updating a second URL mapping table under the condition that the services in the single architecture system are detected to be split into the micro-service.

In the above embodiment, the second Zuul configuration component and the second routing locator are registered in the second dynamic router, so that the second dynamic router can determine a specific micro-service interface corresponding to the second URL based on the second Zuul configuration component, and call the micro-service interface through the second routing locator, thereby implementing that the user uses the URL of the micro-service before being split from the single architecture system to access the interface of the micro-service.

In one possible implementation manner, before determining whether the service corresponding to the first URL is a micro service based on the first URL mapping table, the method further includes: acquiring an IP address of a first URL transmitting end network device; judging whether the network equipment has authority for accessing the service interface corresponding to the first URL or not based on the URL interface access authority table; the URL interface access authority table comprises IP address information with service interface authorities corresponding to access first URLs; if yes, based on the first URL mapping table, whether the service corresponding to the first URL is a micro service is judged. Therefore, the first dynamic router can reject the network equipment without access authority to access the service interface, and avoid the data leakage of the service or the micro-service in the monomer architecture system, thereby causing the information security problem.

In one possible implementation manner, before determining whether the service corresponding to the first URL is a micro service based on the first URL mapping table, the method further includes: judging whether the first URL is the URL in the monomer architecture system or not; if so, judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table; if not, calling a default route.

In a second aspect, an embodiment of the present application provides a forwarding apparatus for a URL, where the apparatus includes: the device comprises a receiving module, a judging module, a converting module and a forwarding module, wherein:

the receiving module is used for receiving the first URL;

the judging module is used for judging whether the service corresponding to the first URL is a micro service or not based on the first URL mapping table;

the conversion module is used for converting the first URL into a second URL of the target micro-service interface;

and the forwarding module is used for sending the second URL to a second gateway.

In one possible implementation manner, the forwarding device of the URL further includes:

the splitting module is used for splitting part of services in the single architecture system into a plurality of micro services according to the service types;

the URL configuration module is used for configuring second URLs of the micro service interfaces;

the first configuration module is used for configuring the first gateway;

And the second configuration module is used for configuring the second gateway.

In one possible implementation manner, the first configuration module further includes:

the first routing module is used for a first dynamic router;

the first registration module is used for registering the first Zuul configuration component and the first route locator in the first dynamic router;

and the first monitoring registration module is used for configuring the first service monitoring component in the first dynamic router.

and the right configuration module is used for configuring the right management component in the first dynamic router.

In one possible implementation manner, the second configuration module includes:

the second routing module is used for establishing a second dynamic router;

a second registration module configured to register a second Zuul configuration component and a second route locator in a second dynamic router;

and the second monitoring registration module is used for configuring a second service monitoring component in the second dynamic router.

the IP address acquisition module is used for acquiring the IP address of the first URL transmitting end network equipment;

And the permission judging module is used for judging whether the network equipment has permission to access the service interface corresponding to the first URL or not based on the URL interface access permission table.

the URL judgment module is used for judging whether the first URL is the URL in the monomer architecture system or not;

and the route calling module is used for calling the default route.

In a third aspect, an embodiment of the present application provides a forwarding device for a URL, where the device includes: one or more processors and memory; the memory is coupled to the one or more processors, the memory for storing computer program code, the computer program code comprising computer instructions that the one or more processors call to cause the electronic device to perform the steps of: receiving a first URL; judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table; under the condition that the service corresponding to the first URL is the micro-service, converting the first URL into a second URL of a target micro-service interface; and sending the second URL of the target micro-service interface to a second gateway.

In one possible implementation, before the processor invokes the computer instructions to cause the device to receive the first URL, the method further includes splitting a portion of services in the monolithic architecture system into a plurality of micro-services according to a service type; configuring a second URL of the plurality of micro-service interfaces; configuring a first gateway; and configuring a second gateway, wherein the second gateway is used for calling the target micro-service interface based on the second URL.

In one possible implementation, the processor invoking the computer instructions to cause the device to configure the first gateway includes: establishing a first dynamic router; registering a first Zuul configuration component and a first route locator in a first dynamic router; a first service monitoring component is configured in a first dynamic router.

In one possible implementation, the processor invokes the computer instructions to cause the device to configure the first gateway further comprising: a rights management component is configured in the first dynamic router.

In one possible implementation, the processor invoking the computer instructions to cause the device to configure the second gateway includes: establishing a second dynamic router; registering a second Zuul configuration component and a second route locator in a second dynamic router; a second service monitoring component is configured in a second dynamic router.

In one possible implementation manner, before the processor invokes the computer instructions to cause the device to determine, based on the first URL mapping table, whether the service corresponding to the first URL is a micro-service, the method further includes: acquiring an IP address of a first URL transmitting end network device; judging whether the network equipment has authority for accessing the service interface corresponding to the first URL or not based on the URL interface access authority table; if yes, based on the first URL mapping table, whether the service corresponding to the first URL is a micro service is judged. In one possible implementation manner, before the processor invokes the computer instructions to cause the device to determine, based on the first URL mapping table, whether the service corresponding to the first URL is a micro-service, the method further includes: judging whether the first URL is the URL in the monomer architecture system or not; if so, judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table; if not, calling a default route.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium comprising instructions which, when run on a forwarding device of a URL, cause the device to perform a method as described in the first aspect or any one of the possible implementations of the first aspect.

Drawings

FIG. 1 is a schematic diagram of a circuit structure according to an embodiment of the present application;

FIG. 2 is a flowchart of a URL forwarding method according to an embodiment of the present application;

fig. 3 is a flowchart of configuring a first gateway according to an embodiment of the present application;

FIG. 4 is an exemplary preset interface diagram provided by an embodiment of the present application;

fig. 5 is a flowchart of configuring a second gateway according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a forwarding device for URL provided in the present application;

fig. 7 is a schematic structural diagram of a forwarding device for URLs according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application for the embodiment. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly understand that the embodiments described herein may be combined with other embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The terms first, second, third and the like in the description and in the claims and in the drawings are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprising," "including," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion. For example, a series of steps or elements may be included, or alternatively, steps or elements not listed or, alternatively, other steps or elements inherent to such process, method, article, or apparatus may be included.

Only some, but not all, of the details relating to the application are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or at the same time. Furthermore, the order of the operations may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, and the like.

As used in this specification, the terms "component," "module," "system," "unit," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a unit may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or being distributed between two or more computers. Furthermore, these units may be implemented from a variety of computer-readable media having various data structures stored thereon. The units may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., second unit data from another unit interacting with a local system, distributed system, and/or across a network).

The single architecture system is an integral architecture system, all functional units of the whole system are deployed in the same process, and in the single architecture system, all services have strong coupling, so that when a certain service in the single architecture system has a problem, all services in the whole single architecture system may not work normally, or when the URL of a certain service interface in the single architecture system needs to be changed, the URL of all service interfaces in the single architecture system also needs to be changed, which results in great consumption of manpower and material resources when the single architecture system needs to be updated.

For ease of understanding, the relationships of the various components in the circuit architecture may be employed to illustrate the relationships of the various services in the monolithic architecture system. As shown in fig. 1, the service a, the service B and the service C in the single architecture system are like the lamps 1, 2 and 3 in the circuit, and the three lamps are in a series relationship, when one of the lamps is turned off, the other two lamps are turned off, so that the relationship between the services in the single architecture system is also that the service B and the service C cannot work normally when the service a cannot work. And with the continuous improvement of the service complexity and the increase of the service code quantity of the system, the single architecture system is more and more bulky, and the coupling degree is higher and higher. Therefore, it is desirable to decouple the individual functional modules or services in a monolithic architecture system so that the individual services or functional modules can operate relatively independently of each other to improve the operational performance of the system. The process of decoupling each service or functional module in the monolithic architecture system is the process of transforming the monolithic architecture system into a micro-service architecture system.

The micro-service is to split a plurality of services with strong coupling in an original complex monomer architecture system into a plurality of independent micro-services, each micro-service maintains own business logic, data processing and deployment, the micro-services communicate with each other through a simple communication protocol (such as a restful API), each micro-service can be written in different languages, and the URL of a micro-service interface is generally regular and has a service name of a unified prefix. The relation among the services in the micro-service architecture system can be understood as the relation among the parallel components in the circuit, and the micro-services or the functional modules are relatively independent, so that the working efficiency of the system is greatly improved.

In the process of modifying a general monomer architecture system into a micro-service system, the whole modification is impossible to be used on line, and in the modification process, if the URL of a service interface of the monomer architecture system is not modified at the front end, the problem that the URL of the monomer architecture system cannot be mapped to the URL of the micro-service interface exists.

In order to solve the problem that in the process of upgrading and transforming a single architecture system into a micro service system architecture, a service interface in the single architecture system is transformed into a micro service interface, so that when a user uses a URL of the single architecture system to access/call the interface transformed into the micro service, the single architecture system cannot map the URL received by the single architecture system into the URL of the micro service interface, thereby causing that the user cannot access the micro service interface, the embodiment of the application provides a forwarding method of the URL, which comprises the following steps: after the gateway layer of the monomer architecture system receives the URL sent by the user, under the condition that the URL is determined to be the URL in the monomer architecture system, the gateway of the monomer architecture system judges whether the service interface corresponding to the URL received by the gateway layer of the monomer architecture system is an interface modified into micro service according to the first URL mapping table stored by the gateway layer of the monomer architecture system. Under the condition that the interface corresponding to the URL received by the gateway is the micro-service interface which is transformed, the gateway of the single-body architecture system can convert the URL received by the gateway of the single-body architecture system into the URL of the corresponding micro-service interface based on the first URL mapping relation table and forward the converted URL to the gateway of the micro-service architecture system, and the gateway of the micro-service architecture system accesses/calls the corresponding micro-service interface based on the converted URL so that a user can call the corresponding service.

Referring to fig. 2, fig. 2 is a flowchart of a URL forwarding method provided by an embodiment of the present application, and the specific flow is as follows:

step S201: the first gateway receives a first URL.

Specifically, the first gateway is a gateway of a single architecture system, the first URL may be a URL in the single architecture system, and the URL in the single architecture system includes a URL of a service interface in the single architecture system that is not split into micro services, and a URL of a service interface in the single architecture system that is split into micro services. For example, as shown in fig. 3, in the single architecture system, the URLs of interfaces corresponding to the three services are url_ A, URL _ B, URL _ C, URL _d, respectively, and when the service a and the service B are split into micro services, the URLs of interfaces of the two services in the micro service architecture system are url_a1 and url_b1, respectively, so that the URLs in the single architecture system of fig. 3 include the URLs of interfaces of the service C and the service D (url_c and url_d) which are not split into micro services, and the URLs of interfaces of the service a and the service B (url_a and url_b) in the single architecture system which are split into micro services.

Alternatively, before the first gateway receives the first URL, the first gateway may be configured, and the configuration procedure of the first gateway is shown in fig. 3. Referring to fig. 3, fig. 3 is a flowchart of configuring a first gateway according to an embodiment of the present application, and the specific flow is as follows:

step S301, a first dynamic router is newly built in the first gateway.

Specifically, a first dynamic router (DynamicRoutesProcessor) is used to invoke service interfaces or route forwarding, i.e.: when the service corresponding to the first URL is the service in the single-body architecture system, the first dynamic router calls a service interface corresponding to the first URL, and when the service corresponding to the first URL is the micro-service, the first dynamic router converts the first URL into the URL of the micro-service interface corresponding to the first URL and sends the converted URL to a gateway of the micro-service architecture system.

Step S302: registering the first dynamic router as a system component, and registering a first Zuul configuration component and a first route locator in the system component.

Specifically, the first Zuul configuration component is configured to store a first URL mapping table, where the first URL mapping table stores a correspondence between a URL of the micro service interface and a URL thereof in the monomer architecture system. Illustratively, the first URL map may be in the form of table 1 as follows:

TABLE 1

Second URL	Third URL	Service identification number
			URL_A	URL_A1	A
URL_B	URL_B1	B
			……	……	……
URL_N	URL_N1	N

The second URL is the URL of the micro service interface in the micro service architecture system, the third URL is the URL of the service interface of the service in the single architecture system before the micro service is split into the micro service, and the service identification number is the identification information of each service and has uniqueness.

The first route locator is used for calling a service interface or performing route forwarding based on the first URL based on a first URL mapping table stored in the first Zuul configuration component. After the first gateway receives the first URL, if the first compoiste routelocator determines that the service interface corresponding to the first URL is a service interface which is not split into micro services in the current monomer architecture system, the first compoiste routelocator calls the service interface based on the first URL. If the first compoiste routelocator determines that the service interface corresponding to the first URL is an interface which has been split into micro services in the single architecture system, the first compoiste routelocator may convert the first URL into a URL (second URL) corresponding to the micro service interface in the micro service system architecture based on the first URL mapping table, and send the converted URL to a gateway of the micro service architecture system.

Step S303: the default route is configured in a first Zuul configuration component.

Specifically, if the URL received by the first gateway of the monomer architecture system is an incorrect URL or a URL that cannot be identified by the first gateway, the first gateway may call a preconfigured first route, so as to display a preset interface on the electronic device. For example, the preset interface may be as shown in fig. 4, and the interface shown in fig. 4 is used to prompt the user to invoke a service error.

Step S304: a first service monitoring component is configured in a first dynamic router.

Specifically, the first service monitoring component is configured to periodically call a gateway of the micro service architecture system through an http interface, obtain a second URL of a service interface migrated to the micro service architecture system, and write a correspondence between the second URL of the micro service interface in the micro service architecture system and a third URL of the micro service interface into a first URL mapping table of the first Zuul configuration component, so as to complete dynamic refresh of the first URL mapping table in the first Zuul configuration component.

It should be understood that step S304 may be performed before step S303, may be performed after step S303, or may be performed simultaneously with step S303, which is not limited in this embodiment of the present application.

Optionally, a rights management component may be configured in the first dynamic router, where the rights management component is configured to perform rights management on a sender device of the received URL, and after the first gateway receives the first URL, the rights management component may obtain an IP address of the sender device according to the first URL, and determine, based on a URL interface access rights table stored in the rights management component, whether the sender network device has a right to access a service interface corresponding to the first URL. If the rights management component judges that the network device at the transmitting end does not have the rights of accessing the service corresponding to the first URL, the rights management component can call a default route and display a preset interface as shown in fig. 4; if the rights management component determines that the sender device has rights to access the service corresponding to the first URL, the first dynamic router executes step S202. Illustratively, the URL interface access rights table may be in the form of table 2:

TABLE 2

The authorized IP address is an IP address with the authority of accessing the corresponding URL service interface. For example, in Table 2, only network devices corresponding to IP-1 and IP-2 may access the service interface corresponding to URL_1, only network devices corresponding to IP-1 and IP-3 may access the service interface corresponding to URL_2, and only network devices corresponding to IP-2 and IP-4 may access the service interface corresponding to URL_N.

By configuring the first gateway of the single-body architecture system by the configuration method in the embodiment of fig. 3, the first gateway of the single-body architecture system can determine whether the service corresponding to the received first URL address is modified into micro service, if so, the first URL address can be converted into the second URL of the micro service interface, and the second URL is sent to the gateway of the micro service architecture system.

Step S202: the first gateway judges whether the service corresponding to the first URL is a micro-service or not based on a first URL mapping table.

Specifically, after receiving the first URL, the first gateway determines whether the service corresponding to the first URL address is modified into the micro service according to the stored first URL mapping table. If the micro service is not modified, the first gateway calls the interface of the service based on the first URL, so that the user can access and call the service, and if the micro service is modified, the first gateway converts the first URL into the second URL of the interface of the micro service based on the first URL mapping table and sends the converted URL to the gateway of the micro service architecture system, so that the gateway of the micro service architecture system can call the corresponding micro service interface based on the converted URL, and the user can access and call the micro service interface.

Step S203: and under the condition that the service corresponding to the first URL is judged to be the micro-service, the first gateway converts the first URL into a second URL of the target micro-service interface.

Specifically, the target micro-service is a micro-service corresponding to a first URL, and the second URL is a URL of the target micro-service interface in the micro-service architecture system.

Step S204: the first gateway forwards the second URL of the target micro-service interface to the second gateway.

Specifically, the second gateway is a gateway of the micro-service architecture system, and the target micro-service interface is an interface of the micro-service corresponding to the first URL.

In one possible implementation, after the first gateway forwards the second URL of the target micro service interface to the second gateway, the second gateway may invoke the target micro service interface based on the second URL, thereby implementing access and invocation of the target micro service by the user.

Alternatively, before the second gateway invokes the target micro service interface based on the second URL, the second gateway may be configured, and the configuration procedure of the second gateway is shown in fig. 5. Referring to fig. 5, fig. 5 is a flowchart of configuring a second gateway according to an embodiment of the present application, and the specific flow is as follows:

Step S501: and a second dynamic router is newly built in the second gateway.

Specifically, a second dynamic router (dynamic router processor) is configured to receive a second URL sent by the first gateway of the monomer architecture system, and call the target micro service interface based on the second URL, so as to access and call the target micro service.

Step S502: registering the second dynamic router as a system component and registering a second Zuul configuration component and a second route locator in the system component.

Specifically, the second Zuul configuration component is configured to store a second URL mapping table, where the second mapping table may include a mapping relationship between the second URL of each micro service interface and the micro service identification information, or may include a mapping relationship between the second URL of the micro service interface, the third URL of the micro service interface, and the identification information of the micro service; the third URL is a URL corresponding to the micro service interface corresponding to the second URL in the single architecture system. The second route locator is used for calling the micro-service interface corresponding to the second URL based on the second URL mapping table and the second URL sent by the first gateway.

Step S503: the default route is configured in a second Zuul configuration component.

Specifically, when the second URL received by the second gateway is an erroneous URL or the second URL received by the second gateway is an unrecognizable URL, the second gateway may call the default route, so that a preset interface is displayed on the electronic device. For example, the preset interface may be as shown in fig. 4, and the interface shown in fig. 4 is used to prompt the user to invoke a service error.

Step S504: a second service monitoring component is configured in a second dynamic router.

Specifically, the second service monitoring component is configured to monitor a second URL generation state of the micro service, and if it is monitored that a new service is disassembled from the single architecture system into the micro service, and the interface of the micro service is configured with the second URL, the service monitoring component may write the mapping relationship between the second URL of the micro service interface, the third URL of the micro service interface, and the identification information of the micro service into the second URL mapping table, so as to dynamically update the second URL mapping table.

It should be understood that step S504 may be performed before step S503, may be performed after step S503, or may be performed simultaneously with step S503, which is not limited in this embodiment of the present application.

The configuration method in the embodiment of fig. 5 is used for configuring the second gateway of the micro-service architecture system, and the second gateway can call the interface of the target micro-service based on the second URL received by the second gateway, so as to realize the access and call of the user to the target micro-service.

In one possible implementation manner, the first gateway may forward the first URL to the second gateway when it is determined that the service interface corresponding to the first URL is a micro service interface, and the second gateway converts the first URL into the second URL based on the second URL mapping table stored in the second gateway, and invokes the target micro service based on the second URL.

In the embodiment of the application, after the monomer architecture system receives the first URL, the gateway of the monomer architecture system judges whether the service interface corresponding to the received URL is an interface modified into micro service according to the stored first URL mapping table under the condition that the URL is determined to be the URL in the monomer architecture system. Under the condition that the interface corresponding to the URL received by the gateway is the micro-service interface which is transformed, the gateway of the single architecture system can convert the URL received by the gateway of the single architecture system into the URL of the corresponding micro-service interface based on the first URL mapping relation table and forward the converted URL to the gateway of the micro-service architecture system, so that the gateway of the micro-service architecture system can access/call the corresponding micro-service interface based on the converted URL, a user can call the corresponding service, the smooth transition of a gateway layer is realized in the process of transforming the single architecture system into the micro-service architecture system, and the problem that the micro-service interface cannot be accessed/called by using the URL in the single architecture system in the process of transforming the single architecture system into the micro-service architecture system is solved, and thus the micro-service cannot be used is solved.

Referring to fig. 6, fig. 6 is a schematic structural diagram of a URL forwarding device provided by the present application. It should be noted that, the forwarding device of URL shown in fig. 6 is used to execute the method of the embodiment of fig. 2 of the present application, for convenience of explanation, only the portion relevant to the embodiment of the present application is shown, and specific technical details are not disclosed, and reference is made to the embodiment of fig. 2 of the present application. The forwarding device 60 of the URL may include: a receiving module 601, a judging module 602, a converting module 603 and a forwarding module 604. Wherein:

A receiving module 601, configured to receive a first URL;

a judging module 602, configured to judge, based on a first URL mapping table, whether a service corresponding to the first URL is a micro service;

a conversion module 603, configured to convert the first URL into a second URL of the target micro service interface;

and the forwarding module 604 is configured to send the second URL to a second gateway.

In one possible implementation manner, the forwarding device 60 of the URL further includes:

the first configuration module is used for configuring the first gateway;

and the second configuration module is used for configuring the second gateway.

the first routing module is used for a first dynamic router;

the second routing module is used for establishing a second dynamic router;

and the route calling module is used for calling the default route.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a URL forwarding device according to an embodiment of the present application. As shown in fig. 7, the forwarding device 70 of the URL includes: at least one processor 701, a memory 702. Optionally, the forwarding device of the URL may further include a network interface 703, where the processor 701, the network interface 703, and the memory 702 are connected to each other through an internal bus 704. Wherein, the processor 701, the memory 702 and the network interface 703 may exchange data, the network interface 703 is controlled by the processor 701 to send and receive messages, the memory 702 is used for storing a computer program, the computer program includes program instructions, and the processor 701 is used for executing the program instructions stored in the memory 702. Wherein the processor 701 is configured to invoke the program instructions to execute the forwarding method of the URL described above.

The memory 702 may include volatile memory (RAM), such as random-access memory (RAM); the memory 702 may also include a non-volatile memory (non-volatile memory), such as a flash memory (flash memory), a Solid State Drive (SSD), etc.; the memory 702 may also include a combination of the above types of memory.

The processor 701 may be a central processing unit (central processing unit, CPU). In one embodiment, the processor 701 may also be a graphics processor (Graphics Processing Unit, GPU). The processor 701 may also be a combination of a CPU and a GPU.

In one possible implementation, the memory 702 is used to store program instructions. The processor 701 invokes the computer instructions to cause the device to perform the steps of: receiving a first URL; judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table; under the condition that the service corresponding to the first URL is the micro-service, converting the first URL into a second URL of a target micro-service interface; and sending the second URL of the target micro-service interface to a second gateway.

In one possible implementation, before the processor 701 invokes the computer instructions to cause the device to receive the first URL, the method further includes splitting a portion of services in the monolithic architecture system into a plurality of micro-services according to a service type; configuring a second URL of the plurality of micro-service interfaces; configuring a first gateway; and configuring a second gateway, wherein the second gateway is used for calling the target micro-service interface based on the second URL.

In one possible implementation, the processor 701 invokes the computer instructions to cause the device to configure a first gateway, including: establishing a first dynamic router; registering a first Zuul configuration component and a first route locator in a first dynamic router; a first service monitoring component is configured in a first dynamic router.

In one possible implementation, the processor 701 invokes the computer instructions to cause the device to configure the first gateway further comprises: a rights management component is configured in the first dynamic router.

In one possible implementation, the processor 701 invokes the computer instructions to cause the device to configure a second gateway, including: establishing a second dynamic router; registering a second Zuul configuration component and a second route locator in a second dynamic router; a second service monitoring component is configured in a second dynamic router.

In one possible implementation manner, before the processor 701 invokes the computer instructions to cause the device to determine, based on the first URL mapping table, whether the service corresponding to the first URL is a micro-service, the method further includes: acquiring an IP address of a first URL transmitting end network device; judging whether the network equipment has authority for accessing the service interface corresponding to the first URL or not based on the URL interface access authority table; if yes, based on the first URL mapping table, whether the service corresponding to the first URL is a micro service is judged.

In one possible implementation manner, before the processor 701 invokes the computer instructions to cause the device to determine, based on the first URL mapping table, whether the service corresponding to the first URL is a micro-service, the method further includes: judging whether the first URL is the URL in the monomer architecture system or not; if so, judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table; if not, calling a default route.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk), etc.

Those skilled in the art will appreciate that implementing all or part of the above-described methods may be accomplished by computer programs, which may be stored on a computer-readable storage medium, and which, when executed, may include the steps of the above-described method embodiments. And the aforementioned storage medium includes: ROM or random access memory RAM, magnetic or optical disk, etc.

In summary, the foregoing description is only an embodiment of the technical solution of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for forwarding URLs, applied to a monolithic architecture system that migrates to a microservice architecture system, the method comprising:

splitting part of services in the single architecture system into a plurality of micro services according to service types;

configuring a second URL of the plurality of micro-service interfaces;

configuring a first gateway, wherein the first gateway is a gateway of the monomer architecture system, and the configured first gateway is used for judging whether the service corresponding to the first URL is a target micro-service or not;

Configuring a second gateway, wherein the configured second gateway is used for calling a target micro-service interface based on a second URL of the target micro-service interface, and the configuring the second gateway comprises the following steps: establishing a second dynamic router, and registering a second Zuul configuration component and a second route locator in the second dynamic router; the second Zuul configuration component comprises a second URL mapping table, wherein the second URL mapping table comprises a mapping relationship between a second URL of a micro service interface and identification information corresponding to the micro service interface, or the second URL mapping table comprises a mapping relationship between the second URL of the micro service interface, a third URL of the micro service interface and identification information corresponding to the micro service interface, and the second routing locator is used for calling the target micro service interface based on the second URL mapping table and the second URL of the target micro service interface;

receiving a first URL, wherein the first URL is a URL in a monomer architecture system;

judging whether the service corresponding to the first URL is a micro-service or not based on a first URL mapping table; the first URL mapping table comprises a mapping relation between a second URL of a micro service interface and a third URL of the micro service interface, wherein the second URL is the URL of the micro service interface in a micro service architecture system, and the third URL is the URL of the micro service interface in a single architecture system;

Converting the first URL into a second URL of a target micro-service interface under the condition that the service corresponding to the first URL is micro-service;

transmitting a second URL of the target micro-service interface to a second gateway; the second gateway is a gateway of the micro-service architecture system, and the second URL of the target micro-service interface is used for the second gateway to call the target micro-service interface.

2. The method of claim 1, wherein the configuring the first gateway comprises:

establishing a first dynamic router;

registering a first Zuul configuration component and a first route locator in the first dynamic router; the first Zuul configuration component is used for storing the first URL mapping table, and the first route locator is used for judging whether the service corresponding to the first URL is a micro-service or not based on the first URL mapping table;

and configuring a first service monitoring component in the first dynamic router, wherein the first service monitoring component is used for periodically calling the second gateway through an http interface, acquiring a second URL of a micro service, and writing the corresponding relation between the second URL of the micro service interface and a third URL of the micro service interface into the first URL mapping table.

3. The method of claim 2, wherein configuring the first gateway further comprises:

and configuring a right management component in the first dynamic router, wherein the right management component is used for carrying out right management of service interface access on the network equipment of the first URL transmitting end.

4. The method of claim 1, wherein the configuring the second gateway further comprises:

and configuring a second service monitoring component in the second dynamic router, wherein the second service monitoring component is used for monitoring a second URL generation state of the micro-service, and dynamically updating the second URL mapping table under the condition that the services in the single architecture system are detected to be split into the micro-service.

5. The method of claim 1, wherein before determining whether the service corresponding to the first URL is a micro-service based on the first URL map, further comprises:

acquiring an IP address of the first URL transmitting end network device;

judging whether the network equipment has authority for accessing the service interface corresponding to the first URL or not based on a URL interface access authority table; the URL interface access authority table comprises IP address information with service interface authorities corresponding to the access first URL;

If yes, judging whether the service corresponding to the first URL is a micro service or not based on the first URL mapping table.

6. The method of claim 1, wherein before determining whether the service corresponding to the first URL is a micro-service based on the first URL map, further comprises:

judging whether the first URL is the URL in the monomer architecture system or not;

if so, judging whether the service corresponding to the first URL is a micro-service or not based on a first URL mapping table;

if not, calling a default route.

7. A URL forwarding apparatus, comprising:

the first configuration module is used for configuring a first gateway, wherein the first gateway is a gateway of the monomer architecture system, and the configured first gateway is used for judging whether the service corresponding to the first URL is a target micro-service or not;

a second configuration module for configuring a second gateway for invoking the target micro-service interface based on a second URL of the target micro-service interface,

Wherein the second configuration module comprises:

the second routing module is used for establishing a second dynamic router;

a second registration module, configured to register a second Zuul configuration component and a second routing locator in the second dynamic router, where the second Zuul configuration component includes a second URL mapping table, the second URL mapping table includes a mapping relationship between a second URL of a micro service interface and identification information corresponding to the micro service interface, or the second URL mapping table includes a mapping relationship between the second URL of the micro service interface, a third URL of the micro service interface, and identification information corresponding to the micro service interface, and the second routing locator is configured to invoke the target micro service interface based on the second URL mapping table and the second URL of the target micro service interface;

the receiving module is used for receiving a first URL, wherein the first URL is a URL in the monomer architecture system;

the judging module is used for judging whether the service corresponding to the first URL is a micro service or not based on the first URL mapping table; the first URL mapping table comprises a mapping relation between a second URL of a micro service interface and a third URL of the micro service interface, wherein the second URL is the URL of the micro service interface in a micro service architecture system, and the third URL is the URL of the micro service interface in a single architecture system;

The conversion module is used for converting the first URL into a second URL of a target micro-service interface under the condition that the service corresponding to the first URL is micro-service;

the forwarding module is used for sending the second URL of the target micro-service interface to a second gateway; the second gateway is a gateway of the micro-service architecture system, and the second URL of the target micro-service interface is used for the second gateway to call the target micro-service interface.

8. An electronic device comprising a processor and a memory, wherein the memory is configured to store a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any of claims 1-6.

9. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method according to any of claims 1-6.