Gateway configuration method and electronic equipment

Abstract

The invention provides a gateway configuration method and electronic equipment, which are used for realizing gateway configuration of a visual interface by dragging a service module and effectively reducing the operation and maintenance difficulty. The method comprises the steps that service modules are displayed on a visual interface, the visual interface comprises a published area and a non-published area, the published area is used for displaying service modules of published services, and the non-published area is used for displaying service modules of non-published services; and in response to an operation that a user drags a target service module from a non-published area to a published area, performing corresponding gateway configuration on the target service module, and running a service corresponding to the target service module, the target service module being selected by the user from service modules which are not run in the non-published area.

Description

Gateway configuration method and electronic device Technical Field

[0001] The present disclosure relates to the technical field of service maintenance, and in particular to a gateway configuration method and electronic device. Background Art

[0002] In network transmission, gateways primarily provide network protection and routing functions. In software development, gateways are often integrated with microservices, serving as the entry point for the entire service, facilitating authentication and authorization, routing, load balancing, and other functions. For users, gateway configuration is most commonly used to manage and maintain microservices.

[0003] Currently, gateway configuration is usually managed through a form, which is not convenient for subsequent maintenance.

[0004] Summary of the Invention

[0005] The present disclosure provides a gateway configuration method and electronic device, which are used to implement gateway configuration on a visual interface by dragging and dropping service modules, effectively reducing the difficulty of operation and maintenance.

[0006] In a first aspect, an embodiment of the present disclosure provides a gateway configuration method, the method comprising:

[0007] Displaying service modules on a visual interface, wherein the visual interface includes a published area and an unpublished area, wherein the published area is used to display service modules of published services, and the unpublished area is used to display service modules of unpublished services;

[0008] In response to a user's operation of dragging a target service module from an unpublished area to a published area, a corresponding gateway configuration is performed on the target service module, and a service corresponding to the target service module is run, wherein the target service module is selected by the user from service modules that are not running in the unpublished area.

[0009] In a second aspect, an embodiment of the present disclosure provides an electronic device, including a processor and a memory, wherein the memory is configured to store a program executable by the processor, and the processor is configured to read the program in the memory and perform the following steps:

[0010] Displaying service modules on a visual interface, wherein the visual interface includes a published area and an unpublished area, wherein the published area is used to display service modules of published services, and the unpublished area is used to display service modules of unpublished services;

[0011] In response to a user's operation of dragging a target service module from an unpublished area to a published area, a corresponding gateway configuration is performed on the target service module, and a service corresponding to the target service module is run, wherein the target service module is selected by the user from service modules that are not running in the unpublished area.

[0012] In a third aspect, an embodiment of the present disclosure further provides a gateway configuration device, the device comprising:

[0013] A service display unit, configured to display service modules on a visual interface, wherein the visual interface includes a published area and an unpublished area, wherein the published area is configured to display service modules of published services, and the unpublished area is configured to display service modules of unpublished services;

[0014] The gateway configuration unit is used to perform corresponding gateway configuration on the target service module and run the service corresponding to the target service module in response to the user's operation of dragging the target service module from the unreleased area to the released area, wherein the target service module is selected by the user from the service modules that are not running in the unreleased area.

[0015] In a fourth aspect, an embodiment of the present disclosure further provides a computer storage medium on which a computer program is stored, which, when executed by a processor, is used to implement the steps of the method described in the first aspect above.

[0016] These and other aspects of the present disclosure will become more readily apparent from the following description of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0018] 1A-1B are schematic diagrams of a gateway configuration interface in form provided by an embodiment of the present disclosure;

[0019] FIG2 is a flowchart of a specific implementation of a gateway configuration method provided by an embodiment of the present disclosure;

[0020] 3A-3D are diagrams of a gateway configuration management interface provided by an embodiment of the present disclosure;

[0021] FIG3E is a schematic diagram of a service layered call provided by an embodiment of the present disclosure;

[0022] FIG4 is a diagram of an anonymous gateway configuration interface provided by an embodiment of the present disclosure;

[0023] FIG5 is an interface diagram of a route matching function provided by an embodiment of the present disclosure;

[0024] FIG6 is a service diagram of a visual interface provided by an embodiment of the present disclosure;

[0025] FIG7 is a diagram of a gateway configuration interface showing different operating states provided by an embodiment of the present disclosure;

[0026] FIG8 is a diagram of a gateway configuration interface showing a connection status provided by an embodiment of the present disclosure;

[0027] FIG9 is a diagram of a gateway configuration interface corresponding to sub-areas and service module colors provided by an embodiment of the present disclosure;

[0028] 10A-10B are initial diagrams of a gateway management interface configuration provided by an embodiment of the present disclosure;

[0029] 10C-10D are exemplary diagrams showing a completed gateway interface configuration according to an embodiment of the present disclosure;

[0030] FIG11A is a schematic diagram of an auxiliary service configuration interface provided by an embodiment of the present disclosure;

[0031] FIG11B is a schematic diagram of a functional service configuration interface provided by an embodiment of the present disclosure;

[0032] FIG11C is a schematic diagram of a stealth service configuration interface provided by an embodiment of the present disclosure;

[0033] FIG11D is a schematic diagram of an anonymous service configuration interface provided by an embodiment of the present disclosure;

[0034] FIG12 is a diagram of a visual interface after an auxiliary service and a hidden service are added according to an embodiment of the present disclosure;

[0035] 13A-13B are schematic diagrams of a service release provided by an embodiment of the present disclosure;

[0036] FIG13C is an interface diagram of a service provided by an embodiment of the present disclosure after publishing is completed and running normally;

[0037] FIG14A is an interface diagram of an add function service provided by an embodiment of the present disclosure;

[0038] FIG14B is an interface diagram after a service release is completed according to an embodiment of the present disclosure;

[0039] 15A-15B are diagrams of a level adjustment interface after a functional service is launched according to an embodiment of the present disclosure;

[0040] FIG16A is a diagram of a service interface formed by a service offline provided by an embodiment of the present disclosure;

[0041] FIG16B is an interface diagram of a multi-level service module provided by an embodiment of the present disclosure;

[0042] FIG16C is a diagram of an interface for offline service provided by an embodiment of the present disclosure;

[0043] 17A-17B are diagrams showing a configuration interface of an anonymous service provided by an embodiment of the present disclosure;

[0044] FIG18 is a flow chart showing the operation principle of a gateway service provided by an embodiment of the present disclosure;

[0045] FIG19 is a schematic diagram of an electronic device provided by an embodiment of the present disclosure;

[0046] FIG20 is a schematic diagram of a gateway configuration device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0047] To make the objectives, technical solutions, and advantages of the present disclosure more clear, the present disclosure will be further described in detail below with reference to the accompanying drawings. It is apparent that the embodiments described are only a portion of the embodiments of the present disclosure, rather than all of them. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present disclosure without creative effort are intended to fall within the scope of protection of the present disclosure.

[0048] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0049] The application scenarios described in the embodiments of the present disclosure are intended to more clearly illustrate the technical solutions of the embodiments of the present disclosure and do not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Persons skilled in the art will appreciate that, as new application scenarios emerge, the technical solutions provided by the embodiments of the present disclosure will also be applicable to similar technical problems. In the description of the present disclosure, unless otherwise specified, "multiple" means two or more.

[0050] In this "Internet+" era, computer systems are becoming increasingly intertwined with our lives. More and more systems are being incorporated into computer system management, leading to an ever-expanding software landscape, evolving from monolithic services to microservices to clustered services, and the overall complexity of the system. As service systems grow, ensuring high availability, high performance, and high concurrency requires not only service components (such as LVS and Nginx) but also the processing of the services themselves. Gateways were created to address these operational challenges, demonstrating their importance. Therefore, mistakes in gateway configuration and maintenance are crucial to avoid service unavailability.

[0051] The Gateway mainly exists in the form of network protection, routing and forwarding in network transmission. In software project development, the use of gateways is mostly combined with microservices. As the entrance to the entire service, the gateway takes into account a series of functions such as authentication and authorization, routing and forwarding, and load balancing. However, these are low-level functions for developers. For users, the most commonly used method is to manage and maintain microservices through gateway configuration. The current gateway configuration is usually managed in the form of a form, which is not convenient for later maintenance. As shown in Figures 1A and 1B, this embodiment provides a schematic diagram of a gateway configuration interface in the form of a form, in which related functional interfaces such as route matching, gateway current limiting, and anonymous routing are separated. Although such a configuration management interface can meet the needs of software use, maintenance and management require a lot of manpower. In particular, the larger the microservice system, the more obvious this problem is.

[0052] A gateway configuration method provided in this embodiment has a core idea of ​​implementing gateway configuration of services by dragging service modules in a visual interface. This embodiment divides the visual interface into two parts: one is a published area for displaying published and running service modules, and the other is an unpublished area for displaying unpublished and non-running service modules. By dragging an unpublished service module from the unpublished area to the published area, the unpublished service module can be put online, run, and perform corresponding gateway configuration on the service module, thereby facilitating maintenance and reducing the difficulty of operation and maintenance.

[0053] As shown in FIG2 , the specific implementation process of a gateway configuration method provided in this embodiment is as follows:

[0054] Step 200: Displaying service modules on a visual interface, wherein the visual interface includes a published area and an unpublished area. The published area is used to display service modules of published services, and the unpublished area is used to display service modules of unpublished services.

[0055] In practice, the service module in this embodiment is obtained by encapsulating the services to be configured in the system.

[0056] This embodiment divides the visualization interface into two main sections: a published area, which displays service modules for published, live, or running services; and an unpublished area, which displays service modules for unpublished, offline, or stopped services. Unpublished services do not exist in themselves; they exist only as service data and do not provide external functionality.

[0057] Optionally, the published area in this embodiment includes multiple sub-areas, each sub-area is used to display service modules of different service types. The multiple sub-areas in this embodiment include but are not limited to functional sub-areas, anonymous sub-areas, auxiliary sub-areas, stealth sub-areas and gateway sub-areas.

[0058] The service modules in this embodiment are divided into the following types according to different service types:

[0059] Functional service module, anonymous service module, auxiliary service module, stealth service module, gateway service module. Each service type of service module corresponds to different obligations in the entire system. Except for the gateway service module, the power of other service modules comes from the gateway service itself.

[0060] As shown in Figures 3A-3D, this embodiment also provides a gateway configuration management interface diagram, including a published area and an unpublished area, each for displaying service modules within the respective area. As shown in Figure 3A, the published area includes multiple subareas: a functional subarea, an anonymous subarea, an auxiliary subarea, a hidden subarea, and a gateway subarea. In practice, the functional subarea displays functional service modules; the anonymous subarea displays anonymous service modules; the auxiliary subarea displays auxiliary service modules; the hidden subarea displays hidden service modules; and the gateway subarea displays gateway service modules.

[0061] As shown in Figure 3B, the visualization interface in this embodiment can also display the gateway configuration parameters of each service module, such as route matching data (matching route), " / park / " accesses the park service, and " / park / industry / " accesses the industrial park service. This is to ensure that functional services can both isolate data and interact with each other.

[0062] Optionally, this embodiment also provides a concept of service hierarchy, where the smaller the level, the lower the level of the functional service, similar to the pyramid model, following a principle that the upper-level functional service cannot call the lower-level service, that is, the larger level cannot call the smaller level, and the smaller level can call the larger level. The hierarchy of services is determined based on the calling relationship between services, and the specific calling relationship can be determined according to the order of the matched services in the routing matching. As shown in Figure 3E, this embodiment also provides a schematic diagram of service hierarchical calling, for example, dividing services into five levels, from bottom to top, the first level, the second level, the third level, the fourth level, and the fifth level. The first-level service can call the second-level, third-level, fourth-level, and fifth-level services, the second-level service can call the third-level, fourth-level, and fifth-level services, the third-level service can call the fourth-level and fifth-level services, and the fourth-level service can call the fifth-level service.

[0063] As shown in Figure 3B, this embodiment displays two hierarchical areas in the functional sub-area, including a first-level functional area and a second-level functional area. The first-level functional area is used to display first-level services, and the second-level functional area is used to display second-level services. Functional services in the first-level functional area can call data from functional services in the second-level functional area, but functional services in the second-level functional area cannot call data from functional services in the first-level functional area. Within the park service, a path beginning with " / industry / " indicates access to industrial park service data, but park service data cannot be accessed from within the industrial park service.

[0064] As shown in FIG3C , this embodiment can also display the operating status of each service module, allowing users to understand the operating status of each service in the system, thereby rationally allocating hardware resources and achieving load balancing. It should be noted that the display of the operating status by squares of different colors in the figure is only an example. This embodiment can also use different icons such as “good”, “normal”, “abnormal” and other icons to represent different operating states, and can also use direct text display to represent the operating status. Optionally, it is also possible to use charts / texts to indicate whether the code call is normal in the system, whether the library file is referenced or referenced normally, and to use “logs” / ”mapping tables” to correspond charts / texts.

[0065] As shown in FIG3D , this embodiment can also display the calling relationship between services corresponding to each service module, so that users can understand the flow of service data, realize a clear view of the service data in the system, improve operation and maintenance efficiency, and reduce operation and maintenance difficulty.

[0066] It should be noted that the calling relationship between the services corresponding to the two service modules in this embodiment specifically includes: the starting point of the calling relationship represents that the executed code is supported by module A through the interface / port of A; the end point of the call represents that the executed code is supported by other modules to module B, which is implemented by the interface / port of B. For example, the access path of service A is path=a, the path of service B is path=b, and the path of service C is path=c. If service B and service C in the entire microservice are lower-level services of service A, such as service A is at the first level and service B and service C are at the second level, then the actual call APIs generated for service B and service C are / a / b and / a / c respectively; when the request path is / a / b / *, service A will be accessed first, then data will be obtained from service B according to the logical rules of service A, and finally a response will be returned from service A. The same applies to accessing / a / c / *. This embodiment divides different services into different levels. First, it can meet business needs. For example, when the current business responds, in addition to the data of service A, it may also need the data of service B. Second, it can reduce the complexity of the system externally, reduce the number of services visible to the outside world, and improve horizontal expansion performance.

[0067] In some embodiments, the service module in the published area of ​​this embodiment includes a function service module, and the function service module is used to provide corresponding function services for the user; the published area includes a function sub-area, and the function sub-area is used to display the function service module;

[0068] The hierarchy of functional services corresponding to the functional service modules is displayed; the functional service modules corresponding to functional services of different hierarchies are displayed in different functional areas of the functional sub-areas; functional services of higher hierarchies among functional services of different hierarchies can call functional services of lower hierarchies.

[0069] In practice, after receiving an access request, the service level is determined based on the order of services matched by the routes in the route matching rules. Similarly, the levels of different services are divided based on the order of services matched by the routes in the route matching rules. It should be noted that the calling relationship between services in this embodiment is determined based on the order of services matched by the routes in the route matching rules. Among them, according to the route matching rules, the service that is matched first is a higher-level service, and the services that are matched later are all lower-level services relative to the first matched service.

[0070] Step 201: In response to a user dragging a target service module from an unreleased area to a released area, a corresponding gateway configuration is performed on the target service module, and a service corresponding to the target service module is run, wherein the target service module is selected by the user from service modules that are not running in the unreleased area.

[0071] During implementation, users can drag and drop service modules from the unreleased area to the released area, thereby releasing the unreleased service modules. When releasing the service modules, users only need to drag and drop the service modules, and the system will automatically configure the gateway for the service modules to ensure the normal operation of the service modules. Among them, when adding a service module, a required item is included, which is the matching path (access path) path, and the path has certain rule restrictions, such as not containing characters such as / , *, ?, etc. that have other meanings in regular matching. After the service module is added, when the service module is associated, the route of the current service module will be automatically generated according to the upstream service and stored in the database. For example, now add a Qingyang Industrial Park service (path = qy), and when deploying the service, the Qingyang Industrial Park service will be hung under the Industrial Park service (Industrial Park service path = industry, and there is no service above the Industrial Park service). At this time, the real request path of the Qingyang Industrial Park service (path = / industry / qy) will be automatically generated, thereby realizing automatic configuration of the gateway.

[0072] When the published area includes multiple sub-areas, namely functional sub-areas, anonymous sub-areas, auxiliary sub-areas, invisible sub-areas and gateway sub-areas, drag the target service module to the corresponding sub-area according to the sub-area to which the target service module belongs to realize the automatic gateway configuration of the target service module.

[0073] In some embodiments, the service module in this embodiment includes any one or more of the following service types:

[0074] (1) Functional service module, which represents the functional service that provides functions for the user object;

[0075] During implementation, functional services are managed by the gateway service, and users can customize the addition or deletion of services.

[0076] Each functional service can be configured with the required path PATH, current limiting, request path processor, and fan-out of the routing service (i.e., the downstream functional service called) as needed. The " / " separated in the entire PATH is actually the name of each functional service, and the functional service to be accessed is determined based on the maximum matching principle, where the maximum matching principle refers to determining the functional service to be accessed based on the path with the maximum matching degree.

[0077] (2) Anonymous service module, which represents an anonymous service that provides functions for functional services. The anonymous service does not require permission authentication when accessing the functional services;

[0078] In practice, anonymous services do not require permission authentication for access, meaning they are unrestricted. The anonymous service referred to here does not exist per se, but is instead an ancillary service to the functional service.

[0079] In this embodiment, "no permission verification required" means that certain APIs can be accessed anonymously, without authentication. For example, a login interface may not be authenticated successfully, but user information is required to determine whether the current user can be authenticated successfully. For another example, some news platforms want all users to have access to all news content on the platform, but they also want to minimize user operation complexity. In this case, the news acquisition interface can be fully open, accessible to anyone, at any time, and in any situation, without restrictions.

[0080] It's important to note that anonymous services aren't truly services; they simply provide anonymous access to a specific service. Therefore, when adding anonymous services, you can only add them to services that have already been added to your current environment. Furthermore, the anonymous service only works if the service it's attached to is running.

[0081] During implementation, users can add corresponding anonymous service modules based on the functional service modules in the current visual interface. One functional service module corresponds to one anonymous service module. If the functional service module corresponding to the added anonymous service module is in the published area, it means that the functional service module is in the running state, and the anonymous service module can also run at this time. If the functional service module corresponding to the added anonymous service module is in the unpublished area, it means that the functional service module is in the non-running state, and the anonymous service module cannot run at this time.

[0082] As shown in Figure 4, this embodiment provides an anonymous gateway configuration interface diagram, in which, when adding anonymous services, anonymous services can only be added for "campus services", "equipment services", "transportation services", "report services" and "financial services", but the anonymous services added for "financial services" cannot be run because the financial services are not in operation at this time.

[0083] During implementation, only one anonymous service can be configured for the same functional service, but multiple paths can be configured simultaneously and the paths must be absolute. Wildcards can be used (e.g., "*" indicates that only one string can be followed and " / " cannot be included, and "**" indicates no restrictions). However, from a data security perspective, their use is not recommended. Regarding the request method, all request methods are accepted by default, i.e., "*". As shown in Figure 3D, access with the same path as " / park / login" and a request method of "POST" does not require permission authentication. For paths starting with " / park / anonymous / ", no permission authentication is required for any request.

[0084] (3) Auxiliary service module, which represents the auxiliary service that provides functions for the functional service; the auxiliary service is not necessary for the functional service.

[0085] In practice, auxiliary services are managed by the gateway service, allowing users to add or delete them. Auxiliary services may be invisible to the outside world, but once an intrinsic relationship is established between them and the functional services, they can provide essential functionality for them. As shown in Figure 3D, even though the park service itself lacks user functionality, it relies on the support of the user service. Therefore, the user service indirectly provides user functionality to the park service. Authentication services and financial services exist in the same way. Auxiliary services can be accessed using the functional service PATH + the auxiliary service PATH. For example, to access user information for the park service, use " / park / user / ".

[0086] (4) Stealth service module, which means a stealth service that provides functions for functional services and is invisible to the outside world. It can be understood that users cannot access the service.

[0087] During implementation, hidden services are managed by the gateway service. Users can customize the addition or deletion of hidden services, providing externally invisible features for the functional services themselves, such as scheduled tasks, scheduling, and messaging. For example, the Qingyang Industrial Park service in Figure 3D is unreachable (inaccessible) via " / park / industry / qy / " or " / finical / first / qy / ." Hidden services implement functionality required by multiple functional services, avoiding duplication of functionality across multiple services. For example, if both the Industrial Park service and the First Branch of China Construction Bank need to perform personnel flow statistics and identification, the scheduled task function of the Qingyang Industrial Park service can support personnel flow statistics and identification during specific time periods. For example, if both the Industrial Park service and the First Branch of China Construction Bank need to perform scheduled video recording, the scheduled task and scheduling functions of the Qingyang Industrial Park service can support recording of both the Industrial Park service and the First Branch of China Construction Bank during specific time periods. The scheduling function receives and processes the scheduling data, and then feeds the results back to the Industrial Park service and the First Branch of China Construction Bank. Similarly, when both the Industrial Park Service and the First Branch of China Construction Bank need to send and receive messages, the Qingyang Industrial Park Service's messaging function can be used to send and receive messages between the Industrial Park Service and the First Branch of China Construction Bank. Using stealth services, identical sub-functions within different functional services can be extracted and implemented through stealth services, reducing the need for repeated execution of the same functions by different functional services.

[0088] The difference between stealth service and auxiliary service is that stealth service never provides any functions to the outside world, while auxiliary service can provide specific functions when any functional service is connected to it.

[0089] (5) Gateway service module, which manages all services except itself.

[0090] The gateway service in this embodiment is the cornerstone of the entire system, requiring no user management. It provides management functions for all services (such as the layout of the entire visual interface and basic service data management), service request forwarding and return (route matching), and service status monitoring (real-time operational data such as the operating status of each service in the system and the connection status (network status) between services). As shown in Figure 5, this embodiment provides an interface diagram for the route matching function. When a user selects the report service, the route " / traffic / report / " is automatically matched based on the path of the selected service.

[0091] When the gateway service performs basic data management functions, each service has a global unique identification field for locating and forwarding the service in the path. As shown in Figure 3D, the identification field of the park service is "park", and its default access path is " / park / ", while the identification field of the industrial park is "industry". However, since it is a secondary service of the park service, its default access path is " / park / industry / ". Therefore, according to the maximum matching principle, it is easy to determine that the service accessed by the path " / park / industry / " is the industrial park service, and the hierarchical relationship between the entire project management services can be intuitively seen, which helps users to more clearly understand the calling relationship between services and the flow of service data based on the hierarchical relationship between services. This is a function that form management does not have.

[0092] This embodiment also includes unpublished services in the unpublished area. The service corresponding to the service module in the unpublished area is the initialization state of the user-added service. It is simply a piece of service data, and the service itself may not exist. If the service itself does not exist, the corresponding service module can be successfully published, but when the heartbeat between the service module and the service body is detected, although the current service module is in the published area, the running state has stopped.

[0093] Throughout the visual interface, the gateway service is the cornerstone service and must be running. If the gateway service is not running, the entire system will naturally be down. The release and operation of invisible services, auxiliary services, and functional services can only be successfully released and run when the gateway service itself is running. Anonymous services, on the other hand, rely on functional services and can only be released and run successfully when the corresponding functional services are running.

[0094] In some embodiments, this embodiment displays at least one piece of information including the service name, service type, operating status, and gateway configuration parameters of the service corresponding to the service module on the visual interface; wherein the service type is determined based on the function provided by the service; and the operating status indicates the load balancing status of the service.

[0095] Optionally, the gateway configuration parameters include at least one of route matching data (matching route) and anonymous route.

[0096] As shown in Figure 6, this embodiment provides a service diagram of a visual interface. This embodiment displays the service name, operating status, gateway configuration parameters (matching route, anonymous route), etc. of each service module in the visual interface. Different colors are used to represent different operating states, and different sub-area background colors are used to represent sub-areas used to display different service types. The module colors of service modules in the unpublished area represent different service types. When a service is published, the color of the service modules in the published area is unified, indicating that the service is online. Different network connection states can also be represented by different colored lines.

[0097] In some embodiments, if the running status of the service corresponding to the service module is displayed, different running statuses are displayed in different ways, and the displayed running status is used to prompt the user to reasonably allocate hardware resources.

[0098] The display method of the running status in this embodiment includes but is not limited to: icons, colors, text, etc. For example, different running states can be expressed by icons of different colors.

[0099] During implementation, different operating states are represented by different colors. It should be noted that representing the operating state by color in this embodiment is only an example. Users can customize the colors or display methods of different operating states. This embodiment does not impose too many restrictions on this. The methods used to distinguish and display the operating states based on this principle all fall within the scope of protection of this disclosure.

[0100] Optionally, as shown in FIG7 , this embodiment provides a diagram of a gateway configuration interface showing different operating states. The operating states in this embodiment include, but are not limited to, any one or more of the following:

[0101] (1) Unknown status;

[0102] Gray indicates the running status. This status occurs in the following situations: the initialization status of a newly added service (from scratch), such as the device service; the offline service (the service corresponding to the service module moved from the released area to the unreleased area); and the service in the released area but with a heartbeat stopped due to reasons such as service downtime or network unreachability, such as the dictionary service. This may be due to a failure of the service itself or a disconnection of the network connection between the services, resulting in a heartbeat detection failure. When the network connection is disconnected, the connection status can be indicated by the red line between the dictionary service and the traffic service.

[0103] (2) First-level frequency request service;

[0104] Blue indicates the running status and low-request services, indicating that the service is called very rarely. You can appropriately streamline resources for this service and reduce operating costs, such as park services, industrial park services, transportation services, and CCB First Branch services.

[0105] (3) Second-level frequency request service;

[0106] Green indicates the running status, indicating normal service requests, moderate service request frequency, and reasonable service configuration, such as authentication service.

[0107] (4) Third-level frequency request service;

[0108] Yellow indicates the running status, indicating a high request frequency and a reasonable service configuration, such as financial services.

[0109] (5) Level 4 frequency request service;

[0110] Orange represents the running status, indicating a high request frequency and an unreasonable service configuration, such as the Qingyang Industrial Park service.

[0111] (6) Fifth-level frequency request service;

[0112] Red indicates the running status, indicating that the request frequency is extremely high and the service configuration is unreasonable, such as user service.

[0113] Among them, the higher the frequency level, the higher the frequency of the request.

[0114] Optionally, in this embodiment, different color blocks may be displayed to indicate a continuous running state. The color of the color block is used to indicate the calling frequency of the service corresponding to the service module, and different color blocks indicate different calling frequencies.

[0115] The call frequency of the services corresponding to each service module is intuitively displayed in the form of color blocks, allowing users to intuitively understand the request frequency, so as to adjust the architecture in real time, adjust bandwidth usage, and lock in target customers with high service demands.

[0116] In some embodiments, the calling relationship between the service modules is represented by the connection lines between the service modules, and the connection status between the services corresponding to the target service module and the service modules in the published area can also be represented by the display method of the connection lines; wherein the connection lines with different display methods represent different connection statuses.

[0117] The display mode of the connection line in this embodiment includes but is not limited to color, line type, thickness, etc. Different connection states are distinguished by at least one of different colors, line types, and thicknesses.

[0118] Optionally, different connection states can be represented by lines of different colors. As shown in FIG8 , this embodiment provides a gateway configuration interface that displays the connection state. The lines between service modules have the following three colors:

[0119] A gray line indicates that when a service moves from the unreleased area to the released area, a connection has been established with the upper-level service, but the network is temporarily disconnected (heartbeat detection is not established).

[0120] Green lines indicate normal connections between services and normal operating networks, such as between park services and industrial park services.

[0121] A red line indicates a network interruption between services, such as between the traffic service and the dictionary service. This may occur because the network is good but the heartbeat between services is interrupted.

[0122] In practice, using color-coded operational status indicators allows users to intuitively understand the operational status of each service across the system, enabling them to rationally allocate hardware resources based on actual needs, ensuring the entire system operates within a reasonable range and improving operational efficiency. Furthermore, this allows users to quickly identify service anomalies throughout the system. Even if the precise location cannot be determined, the fault can at least be localized within a specific area, significantly reducing troubleshooting time, minimizing service downtime, and increasing overall system stability.

[0123] In some embodiments, the published area and the unpublished area are displayed differently;

[0124] The display manner of the service module in the unpublished area is determined according to the service type of the service module, and service modules of different service types are displayed in different manners in the unpublished area.

[0125] Optionally, the display mode of the areas in this embodiment can be distinguished by different area background colors, different text contents, or different icons, and this embodiment does not impose too many restrictions on this.

[0126] Optionally, the display of the service modules in the unpublished area in this embodiment can be distinguished by different module colors, different module themes, or different icons, and this embodiment does not impose too many restrictions on this. Optionally, the module colors of the service modules in the unpublished area vary according to the service type, and the module colors of the service modules in the published area can be set to the same color or different colors. When a service module is moved from the unpublished area to the published area, the color of the service module can change or not change, and this embodiment does not impose too many restrictions on this.

[0127] In some embodiments, the published area includes multiple sub-areas, each sub-area is used to display service modules of the same service type; different sub-areas are used to display service modules of different service types; and different sub-areas have different display modes.

[0128] During implementation, different sub-areas have different background colors. The background color of each sub-area and the module color of the service module in the sub-area can be the same or different, and this embodiment does not impose too many restrictions. As shown in Figure 9, this embodiment provides a gateway configuration interface with corresponding sub-areas and service module colors. For example, blue represents functional sub-areas and functional services; purple represents auxiliary sub-areas and auxiliary services; orange represents invisible sub-areas and invisible services; yellow represents anonymous sub-areas and anonymous services; red represents gateway sub-areas and gateway services; green represents online services; when the service is added, it is in the unpublished area. The module color of the service module can be used to distinguish which sub-area the service module belongs to, such as device services belong to functional services, and scheduling services belong to invisible services. When the service is released, the color of the service module changes to green, indicating that the service is an online service.

[0129] The visualization interface in this embodiment is used to express the calling relationship, hierarchical relationship, etc. between various services in a visual manner, so that users can clearly understand the relationship between various services in the entire system, which can improve the efficiency of system maintenance.

[0130] In some embodiments, before the visual interface displays the service module, the following steps may be performed:

[0131] In response to the user's custom configuration operation on the visualization interface, at least one of the number of areas, area name, area location, area display method, area size, service module displayed in the area, and service type of the service module displayed in the area in the visualization interface is configured accordingly.

[0132] During implementation, users can set the overall layout of the visual interface, including customizing the design of each area and sub-area. For example, the shape, position, color, and other functions of each area can be customized, as shown in Figures 10A and 10B. This embodiment also provides an initial configuration diagram for the gateway management interface. Users can customize each area by dragging the pre-made pattern on the left to the editing area on the right, including information such as the area shape, color, name, position, and size. After the user configuration is completed, as shown in Figures 10C and 10D, this embodiment also provides an example diagram of the completed gateway interface configuration.

[0133] When the gateway interface is configured, only the gateway service is active in the entire system. At this time, users can add various required services to the system in the visual interface.

[0134] In some embodiments, in response to a user's service adding operation in the visual interface, a service configuration interface is displayed, wherein the service configuration interface is used to display various indicators of the service;

[0135] In response to the indicator parameters of the various indicators input by the user, a service module is generated and displayed in the unpublished area.

[0136] In some embodiments, the indicator parameters include service types, and one service type corresponds to one display mode; according to the display mode corresponding to the service type in the indicator parameters input by the user, the service module is displayed in the unpublished area according to the display mode corresponding to the service type.

[0137] During implementation, this embodiment can define different colors for service modules of different service types for distinction. It can also define various sub-areas in the published area for displaying service modules of different service types. It can also define the background color of the sub-area displaying a service type and the module color of the service module of that service type to be the same, so that when the user brings the service module online, he can drag the service module to the sub-area of ​​the same color according to the color of the service module.

[0138] In some embodiments, the service configuration interface is displayed in the following manner:

[0139] In response to a service adding operation by a user on the visual interface, displaying a service configuration interface according to a service type of a service corresponding to the service adding operation;

[0140] Among them, at least one indicator among the multiple indicators displayed on the service configuration interface corresponding to different service types is different.

[0141] Optionally, the user can trigger a service addition operation in the unpublished area, for example, by displaying an add button in the unpublished area, and the user clicking the add button triggers entry into the service configuration interface. For another example, the user performs a click operation (including double-clicking, right-clicking, left-clicking, etc.) in the unpublished area to trigger entry into the service configuration interface. This embodiment does not impose too many restrictions on how to perform the service addition operation.

[0142] As shown in Figure 11A, this embodiment provides a schematic diagram of an auxiliary service configuration interface. Users can configure various indicators and enter indicator parameters in the corresponding indicator columns. For example, when configuring auxiliary services, you can configure the service name, service type, IP or domain name, port, path PATH, interceptor HANDLER, filter FILTER, and version Version.

[0143] As shown in Figure 11B, this embodiment provides a schematic diagram of a functional service configuration interface. Users can configure various indicators and enter indicator parameters in the corresponding indicator columns. For example, when configuring functional services, you can configure the service name, service type, IP or domain name, port, auxiliary service, upstream service, path PATH, interceptor HANDLER, filter FILTER, version Version, stealth service, and auxiliary PATH.

[0144] As shown in Figure 11C, this embodiment provides a schematic diagram of a stealth service configuration interface. The user can configure various indicators by entering indicator parameters in the corresponding indicator column. For example, when configuring a stealth service, the service name, service type, IP or domain name, port, path, HANDLER, filter, version, and stealth service can be configured.

[0145] As shown in Figure 11D, this embodiment provides a schematic diagram of an anonymous service configuration interface. The user can configure various indicators and enter indicator parameters in the corresponding indicator column. For example, when configuring an anonymous service, the service name, anonymous path PATH_1 and the corresponding request method, anonymous path PATH_2 and the corresponding request method can be configured.

[0146] In some embodiments, the indicators in this embodiment include any one or more of the following:

[0147] Service name; service type; IP or domain name; port; path; interceptor; filter; version; auxiliary service; upstream service; downstream service; hidden service; auxiliary path; anonymous path; request method.

[0148] The following are explanations of the above indicators:

[0149] Service Name: Users can customize the name, and the final name is automatically generated according to the rule (Service Name_Version). The generated final name is globally unique within the system, such as Campus Service_v_1.0.

[0150] Service Type: This includes but is not limited to gateway services (fixed value options, no user configuration required), anonymous services, auxiliary services, functional services, and stealth services. To facilitate intuitive judgment of service types, service modules of different service types will display different colors on the visualization interface after configuration. The specific color setting will be determined by the color of the service type currently published on the visualization interface.

[0151] Auxiliary Services: These are configuration options for functional services. You can select from the drop-down list any of the existing auxiliary services in the system. You can configure zero, one, or multiple auxiliary services. After configuring an auxiliary service, you can choose whether to configure an auxiliary path. For example, campus services rely on user services and authentication services, while transportation services rely on dictionary services. Financial services do not rely on any auxiliary services.

[0152] Upstream Service: This is a specific configuration option for a functional service. You can use the drop-down list to select a functional service that has been added to the current system. You can configure 0, 1, or multiple upstream services. If the upstream service does not exist, the default upstream service is the gateway service. If multiple upstream services are configured, the hierarchy is calculated based on the maximum hierarchy of the upstream functional services (see the hierarchy introduction for details). For example, the upstream service of the industrial park service is the park service, and the upstream service of the park service is the gateway service.

[0153] Path: The path specified by the service is unique across the entire system. However, the special character " / " cannot be specified, as it is the default value for the gateway service system. This value automatically generates a hidden message, the requested url_match_pattern, using the rule "url_match_pattern of the upstream service + path of this service + / ." For example, if the path of the park service is "park," the url_match_pattern is " / park / ," and the path of the industrial park service is "indutry." Since the upstream functional service of the industrial park service is the park service, the url_match_pattern of the industrial park service is " / park / industry / ."

[0154] Auxiliary PATH: It is a specific configuration option for the functional service. It specifies the pattern forwarded to the auxiliary service according to the configured auxiliary service. If it is not set, when querying the auxiliary service data, the url pattern used is the current service url_match_pattern + the auxiliary service url_match_pattern; if it is set, the configured auxiliary path is used directly to forward the request. Taking the park service (path "park") as an example, if the auxiliary path is not configured, the url pattern for the data request to the user service (path "user") is / park / user / . If the auxiliary path is configured as / sys-user, the url pattern for the data request to the user service is / park / sys-user / .

[0155] FILTER and HANDLER: These represent filters and interceptors, respectively, encapsulating common operations. Zero, one, or multiple operations can be configured based on business needs. This indicator can be thought of as a hidden service, differing in that hidden services are performed after a successful request to a functional service, while this indicator is performed before that request. These two operations are global to the configured service itself, requiring execution for every request to the functional service.

[0156] Stealth services are specific configuration options for functional services and stealth services. Depending on business needs, zero, one, or multiple stealth services can be configured. These services themselves lack user functionality and primarily provide support for functional services, similarly encapsulating common operations. For example, a scheduling service can delegate all scheduling tasks to a functional service, without requiring the development of scheduling tasks itself.

[0157] It should be noted that the upstream service and upstream functional service in this embodiment have the same meaning, and both are services that can call other services.

[0158] As shown in Figure 12, this embodiment provides a visual interface after the auxiliary service and invisible service are added. The user service, authentication service, and dictionary service are determined to be auxiliary services based on the background color of the auxiliary sub-area, and the task service is determined to be a invisible service based on the background color of the invisible sub-area. After the user adds the service, the service module will be displayed in the unpublished area, and the module color of each service module is the same as the background color of the corresponding sub-area.

[0159] This embodiment allows you to display service releases by dragging and dropping service modules. Once a service is added, it will be formed into individual service modules (components). The service modules themselves and their configurations are visible to the user, but the user does not need to be aware of the actual internal processing flow. Users can drag and drop service modules to launch (i.e., publish, from an unreleased area to a released area) and take services offline (from a released area to an unreleased area).

[0160] In some embodiments, in response to the user dragging the target service module from the unpublished area to the published area, a locking principle may be added, as shown below:

[0161] According to the service type of the target service module, a sub-area of ​​the published area having the same service type as the target service module is activated to prompt the user to drag the target service module to the activated sub-area.

[0162] In practice, as shown in Figures 13A and 13B, this embodiment provides a schematic diagram of service publishing. When a user selects a service module of a different service type, only the sub-area corresponding to the service type is activated. This means that service modules can only be moved between sub-areas within the published area and unpublished areas of the same service type. For example, when a user selects a user service module, only the auxiliary sub-area is activated, and the user can only move the user service module to the auxiliary sub-area. Figure 13C shows an interface after a service is published and running normally. Once the service is published and running normally, the color of the service module changes to distinguish it from the background color of the sub-area in which it is located.

[0163] In some embodiments, after the service is published, the backend will automatically configure the gateway. The specific steps are as follows:

[0164] According to the calling relationship between the target service module and the service modules in the published area, corresponding gateway configuration parameters are configured for the target service module.

[0165] Optionally, the gateway configuration parameters in this embodiment include but are not limited to route matching data, anonymous route data, etc.

[0166] In some embodiments, the calling relationship between the target service module and the service module in the published area is determined by any of the following methods:

[0167] Method 1: determining the calling relationship between the target service module and the service modules in the published area according to the upstream service and / or downstream service in the indicator parameters of the target service module;

[0168] The upstream service is used to call the service corresponding to the target service module, and the downstream service is used to be called by the service corresponding to the target service module.

[0169] Optionally, the target service module and the service module having the calling relationship are connected to display the calling relationship.

[0170] Optionally, a directional marker may be displayed on the connection line, where the directional marker is used to indicate the flow direction of the service data of the service module in the calling relationship.

[0171] In some embodiments, after the directional indicator is displayed on the connection line, the directional indicator indicates that the service data is transmitted from the target service module to the first service module. The calling relationship between the service modules can also be changed by manually dragging the directional indicator on the connection line, as shown below:

[0172] In response to the user dragging the directional marker to point to the second service module, the calling relationship between the target service module and the first service module is updated to the calling relationship between the target service module and the second service module.

[0173] In implementation, taking the directional identifier as an arrow as an example, the arrow points from the target service module to the first service module. The user can modify the service module that has a calling relationship with the target service module by dragging the arrow, and update the calling relationship to the calling relationship between the target service module and the second service module.

[0174] Mode 2: In response to a user's manual connection operation on the target service module and the service module in the published area, determining a calling relationship between the target service module and the service module in the published area.

[0175] In some embodiments, the connection line corresponding to the manual connection operation is displayed; the direction of the connection line is determined based on the starting point and end point of the manual connection operation, and the direction is displayed through a directional marker, which is used to indicate the flow direction of the service data of the service module in the call relationship.

[0176] Optionally, the directional markers in this embodiment include but are not limited to arrows or other directional markers, icons, etc., and this embodiment does not impose too many restrictions on this.

[0177] In some embodiments, after the directional indicator is displayed on the manual connection line, the directional indicator indicates that the service data is transmitted from the target service module to the first service module. The calling relationship between the service modules can also be changed by manually dragging the directional indicator on the connection line, as shown below:

[0178] In response to the user dragging the directional marker to point to the second service module, the calling relationship between the target service module and the first service module is updated to the calling relationship between the target service module and the second service module.

[0179] During implementation, taking the directional mark as an arrow as an example, when the user draws a line by hand and displays an arrow at the end of the line, the arrow points from the target service module to the first service module. The user can modify the service module that has a calling relationship with the target service module by dragging the arrow, and update the calling relationship to the calling relationship between the target service module and the second service module.

[0180] During implementation, taking the addition of a functional service with auxiliary services and invisible services as an example, as shown in FIG14A, this embodiment provides an interface for adding functional services. The interface has currently added the campus service and is running the auxiliary service and invisible service. According to the auxiliary service and invisible service that the campus service itself will call, the user drags the campus service module to the functional sub-area, and the interface after the service is released is shown in FIG14B. The system will automatically connect the called user service and task service according to the calling relationship of the campus service, and the calling relationship between different services is represented by the connection line and arrow. After the campus service is released, the system will automatically connect the auxiliary service and the invisible service according to the service information itself. When a hierarchical functional service is online, only the upper functional service of the functional service can be automatically connected, and the lower functional service of the functional service can be manually connected.

[0181] It should be noted that the call relationship in this embodiment also includes the hierarchical relationship between different functional services. During implementation, after the service is released, the backend will automatically add relevant route matching data based on the call relationship and hierarchical relationship between services, so that the service can determine the direction of data flow during use. At the same time, when the service is offline, the service will also delete the corresponding route matching data to avoid the problem of data misflow or non-return.

[0182] In some embodiments, when there is a hierarchical relationship between functional services, after dragging and dropping to publish, it will automatically adapt to match the level of the current service according to the upstream service of the current service. If the upstream service does not exist, it will be automatically published to the first-level service. If it exists, it will adapt according to the maximum level of the upstream service and associate the connection operation between the upstream service and this service. However, if there is a downstream service, the user can only connect through it.

[0183] It should be noted that the upstream service in the functional sub-area is defined as the upstream functional service in this embodiment, and the downstream service in the functional sub-area is defined as the downstream functional service in this embodiment. In fact, the meanings of upstream service and upstream functional service are the same, and the meanings of downstream service and downstream functional service are the same.

[0184] The first case is the level adjustment after the functional service is launched.

[0185] In some embodiments, in response to a user dragging a target service module from an unreleased area to the functional sub-area, the level of the functional service corresponding to the functional service module in the functional sub-area is adaptively adjusted; wherein the target service module is a functional service module in the unreleased area.

[0186] During implementation, the user drags an unreleased functional service module from the unreleased area to the functional sub-area. If there is a hierarchical relationship between multiple functional service modules in the functional sub-area, the hierarchy of the functional service modules in the dragged functional sub-area is adaptively adjusted.

[0187] In some embodiments, the level of the functional service corresponding to the functional service module in the functional sub-area is adaptively adjusted through the following steps:

[0188] The level of the functional service corresponding to the functional service module is adaptively adjusted according to whether there is an upstream functional service for the functional service corresponding to the functional service module, and the maximum level of the upstream functional service when there is an upstream functional service; wherein the upstream functional service is used to call the functional service corresponding to the functional service module.

[0189] In some embodiments, the level of the functional service corresponding to the functional service module is adaptively adjusted specifically through the following steps:

[0190] If the functional service corresponding to the functional service module does not have an upstream functional service, determining that the level of the functional service corresponding to the functional service module is the maximum level; or

[0191] If the functional service corresponding to the functional service module has an upstream functional service, the level of the functional service corresponding to the functional service module is determined according to the maximum level of the upstream functional service.

[0192] As shown in Figures 15A and 15B, this embodiment provides a hierarchical adjustment interface diagram after the functional service is launched. When the user drags the industrial park service module from the unreleased area to the functional sub-area, since the upstream functional service (i.e., the upper functional service) of the industrial park service is the park service, and the level of the park service is the first level, the level of the industrial park service is determined to be the second level, and the industrial park service is adaptively placed in the functional area of ​​the second level. The number of functional areas contained in the functional sub-area is determined according to the hierarchical structure of the current functional service and is updated in real time. In implementation, it can be seen from the changes in the interface after the service is launched that the system automatically places the industrial park service in the second level and completes the network connection between it and the upper functional service (upstream functional service) park service.

[0193] The second situation is the level adjustment after the functional service is offline.

[0194] In some embodiments, in response to the user dragging a designated service module from the functional sub-area to the unpublished area, the level of the functional service corresponding to the functional service module in the functional sub-area is adaptively adjusted; the designated service module is selected by the user from the functional service modules in the functional sub-area.

[0195] During implementation, after the user drags a functional service module in a functional sub-area to the unreleased area, the functional sub-area adaptively adjusts the hierarchy of each functional service module according to the hierarchical relationship between the remaining functional service modules.

[0196] It should be noted that when hierarchical functional services go offline, service islands may form within the functional sub-areas, causing service unreachability. As shown in Figure 16A, this embodiment provides a service interface for when a service goes offline. When the park service in a functional sub-area goes offline, the industrial park service forms an independent island service, causing service unreachability.

[0197] If a middle-level service is offline, all lower-level services associated with it will be unreachable. As shown in Figure 16B, this embodiment provides an interface diagram of a multi-level service module. In the initial state, the device service and report service can be accessed through " / park / industry / device / " and " / park / industry / report / " respectively, and the report service can be accessed through " / traffic / report / ". However, after the industrial park service is deleted, as shown in Figure 16C, this embodiment provides an interface diagram of a service offline. The device service forms an island and no service is reachable. The previous " / park / industry / report / " cannot access the report service, but " / traffic / report / " can still access the report service normally.

[0198] In some embodiments, this embodiment may further control the service corresponding to the designated service module to be converted from a running state to a non-running state in response to the user dragging the designated service module to the unpublished area, and delete the gateway configuration parameters corresponding to the designated service module;

[0199] The designated service module is selected by the user from the service modules in the published area.

[0200] During implementation, after the user drags a service module from the published area to the unpublished area, the service corresponding to the service module goes offline. At this time, the system automatically deletes the gateway configuration parameters corresponding to the service module, such as route matching data.

[0201] In some embodiments, this embodiment may also delete configuration data corresponding to a service module in an unpublished area in response to a user's deletion operation on the service module, wherein the configuration data includes gateway configuration parameters. The configuration data may also include service-related indicator parameters, such as service name, service type, and other indicator parameters.

[0202] As shown in Figures 17A and 17B, this embodiment also provides an anonymous service configuration interface. After the user adds the anonymous service corresponding to the campus service (campus anonymous gateway service), the user drags the anonymous service to the anonymous sub-area, and the system automatically runs the anonymous service. It should be noted that when adding an anonymous service, only anonymous services of functional services in the currently published area can be added. When running an anonymous service, the anonymous service can only be run when the functional service corresponding to the anonymous service is in the running state.

[0203] During implementation, when configuring anonymous services, we aim for system flexibility by adding configuration information such as filters, handlers, and adapters. This leverages the common features of gateways while also adding plug-in customization capabilities, making gateway configuration management more plug-in-based. The configuration method is largely the same as for services and will not be detailed here.

[0204] For security reasons, all services must be taken offline before physical deletion of service configurations can be performed. That is, services in released areas can only be taken offline and cannot be deleted, while services in unreleased areas are not restricted from being deleted.

[0205] As shown in Figure 18, this embodiment also provides a flow chart of the operation principle of a gateway service. First, the gateway service determines whether the path of the current request is an anonymous path PATH. If so, path matching (route matching) is performed to match the anonymous path PATH. If the match is consistent, it is determined whether the service exists. If the service exists, data is requested and the process ends after the data is returned. Otherwise, the process ends after a prompt that the service does not exist. If the path match is inconsistent, the process ends after a prompt that the path is wrong. If the path of the current request is not an anonymous path PATH, it indicates that it is a protected path PATH, and authorization is requested. If the authorization is successful, path matching is performed, otherwise a prompt that no access permission is given is displayed and the process ends.

[0206] The gateway configuration method provided in this embodiment encapsulates all services involved in the system into modules and places them in the management interface. Users can drag and drop service modules to configure the gateway and the relationships between services, making gateway configuration "visible and available" and reducing the difficulty of using the system.

[0207] This embodiment configures gateway routing by dragging and dropping in a graphical interface, avoiding traditional form-based gateway configuration; the operation interface can display the operating status and service distribution of services within the system with the naked eye, and uses different colors to distinguish and display the operating status of services under the entire system, quickly locating service anomalies in the system, reducing service anomaly troubleshooting time, increasing the stable operation time of services, reasonably allocating hardware resources, and improving the operating efficiency of the system. This reduces the difficulty of maintaining complex systems. The overall picture of the entire system is intuitively displayed in a visual way, and there is no need to be constrained by a single form-based gateway; the operating status of the entire system is also displayed in a visual way, reducing the degree of operation and maintenance and increasing the stability of system operation; the online and offline operations of services are performed by dragging and dropping, and it has extremely strong adaptability; the configuration, release, operation, offline and deletion processes of services in the entire system are manually operated, while adding a locking principle, which greatly increases the security of operation and maintenance.

[0208] Based on the same inventive concept, the embodiment of the present disclosure also provides an electronic device. Since the electronic device is the electronic device in the method in the embodiment of the present disclosure, and the principle of solving the problem by the electronic device is similar to that of the method, the implementation of the electronic device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0209] As shown in FIG19 , the electronic device includes a processor 1900 and a memory 1901 . The memory 1901 is used to store programs executable by the processor 1900 . The processor 1900 is used to read the programs in the memory 1901 and perform the following steps:

[0210] Displaying service modules on a visual interface, wherein the visual interface includes a published area and an unpublished area, wherein the published area is used to display service modules of published services, and the unpublished area is used to display service modules of unpublished services;

[0211] In response to a user's operation of dragging a target service module from an unpublished area to a published area, a corresponding gateway configuration is performed on the target service module, and a service corresponding to the target service module is run, wherein the target service module is selected by the user from service modules that are not running in the unpublished area.

[0212] As an optional implementation manner, the processor 1900 is specifically configured to execute:

[0213] According to the calling relationship between the target service module and the service modules in the published area, corresponding gateway configuration parameters are configured for the target service module.

[0214] As an optional implementation manner, the processor 1900 is specifically configured to determine the calling relationship between the target service module and the service module in the published area by any of the following methods:

[0215] Determine, based on the upstream service and / or downstream service in the indicator parameters of the target service module, the calling relationship between the target service module and the service module in the published area; wherein the upstream service is used to call the service corresponding to the target service module, and the downstream service is used to be called by the service corresponding to the target service module; or

[0216] In response to a manual connection operation performed by a user on the target service module and the service module in the published area, a calling relationship between the target service module and the service module in the published area is determined.

[0217] As an optional implementation manner, if the calling relationship between the target service module and the service module in the published area is determined based on the upstream service and / or downstream service in the indicator parameters of the target service module, the processor 1900 is further configured to execute:

[0218] The target service module and the service module having the calling relationship are connected to display the calling relationship.

[0219] As an optional implementation manner, the processor 1900 is further configured to execute:

[0220] A directional marker is displayed on the connection line, and the directional marker is used to indicate the flow direction of the service data of the service module in the calling relationship.

[0221] As an optional implementation, if, in response to a user manually connecting the target service module and the service module in the published area, the calling relationship between the target service module and the service module in the published area is determined, the processor 1900 is further configured to execute:

[0222] Display the connection corresponding to the manual connection operation;

[0223] The direction of the connection is determined according to the starting point and the end point of the manual connection operation, and the direction is displayed by a direction mark, which is used to indicate the flow direction of the service data of the service module in the call relationship.

[0224] As an optional implementation manner, after a directional indicator is displayed on the connection line, the directional indicator indicates that the service data is transmitted from the target service module to the first service module, and the processor 1900 is further configured to execute:

[0225] In response to the user dragging the directional marker to point to the second service module, the calling relationship between the target service module and the first service module is updated to the calling relationship between the target service module and the second service module.

[0226] As an optional implementation manner, the processor 1900 is further configured to execute:

[0227] The display mode of the connection line indicates the connection status between the target service module and the services corresponding to the service modules in the published area. Connections in different display modes indicate different connection statuses.

[0228] As an optional implementation, the service module in the published area includes a functional service module, which is used to provide corresponding functional services for the user; the published area includes a functional sub-area, which is used to display the functional service module; the processor 1900 is further configured to execute:

[0229] The hierarchy of functional services corresponding to the functional service modules is displayed; the functional service modules corresponding to functional services of different hierarchies are displayed in different functional areas of the functional sub-areas; functional services of higher hierarchies among functional services of different hierarchies can call functional services of lower hierarchies.

[0230] As an optional implementation manner, the processor 1900 is further configured to execute:

[0231] In response to a user dragging a designated service module from the functional sub-area to the unreleased area, adaptively adjusting the hierarchy of the functional services corresponding to the functional service modules in the functional sub-area; the designated service module is selected by the user from the functional service modules in the functional sub-area; or

[0232] In response to a user dragging a target service module from an unreleased area to the functional sub-area, the hierarchy of the functional service corresponding to the functional service module in the functional sub-area is adaptively adjusted; wherein the target service module is a functional service module in the unreleased area.

[0233] As an optional implementation manner, the processor 1900 is specifically configured to execute:

[0234] The level of the functional service corresponding to the functional service module is adaptively adjusted according to whether there is an upstream functional service for the functional service corresponding to the functional service module, and the maximum level of the upstream functional service when there is an upstream functional service; wherein the upstream functional service is used to call the functional service corresponding to the functional service module.

[0235] As an optional implementation manner, the processor 1900 is specifically configured to execute:

[0236] If the functional service corresponding to the functional service module does not have an upstream functional service, determining that the level of the functional service corresponding to the functional service module is the maximum level; or

[0237] If the functional service corresponding to the functional service module has an upstream functional service, the level of the functional service corresponding to the functional service module is determined according to the maximum level of the upstream functional service.

[0238] As an optional implementation manner, the service module includes any one or more of the following service types:

[0239] Functional service module, which represents the functional service that provides functions for the user object;

[0240] Anonymous service module, representing an anonymous service that provides functions for functional services. The anonymous service does not require permission authentication when accessing the functional services;

[0241] Auxiliary service module, which represents the auxiliary service that provides functions for functional services;

[0242] The stealth service module represents a stealth service that provides functionality for the functional service and is not visible to the outside world.

[0243] The gateway service module manages all services except itself.

[0244] As an optional implementation manner, the processor 1900 is further configured to execute:

[0245] On the visual interface, at least one of the following information is displayed: the service name, service type, operating status, and gateway configuration parameters of the service corresponding to the service module; wherein the service type is determined according to the function provided by the service; and the operating status indicates the load balancing status of the service.

[0246] As an optional implementation,

[0247] If the running status of the service corresponding to the service module is displayed, different running statuses are displayed in different ways, and the displayed running status is used to prompt the user to reasonably allocate hardware resources.

[0248] As an optional implementation manner, the processor 1900 is further configured to execute:

[0249] The published area and the unpublished area are displayed in different ways;

[0250] The display manner of the service module in the unpublished area is determined according to the service type of the service module, and service modules of different service types are displayed in different manners in the unpublished area.

[0251] As an optional implementation manner, the released area includes multiple sub-areas, and the sub-areas include functional sub-areas; the processor 1900 is further configured to execute:

[0252] Each sub-area is used to display service modules of the same service type; different sub-areas are used to display service modules of different service types; and different sub-areas have different display modes.

[0253] As an optional implementation manner, in response to the user dragging the target service module from the unpublished area to the published area, the processor 1900 is further configured to execute:

[0254] According to the service type of the target service module, a sub-area of ​​the published area having the same service type as the target service module is activated to prompt the user to drag the target service module to the activated sub-area.

[0255] As an optional implementation manner, the processor 1900 is further configured to execute:

[0256] In response to the user's service adding operation on the visual interface, a service configuration interface is displayed, wherein the service configuration interface is used to display various indicators of the service;

[0257] In response to the indicator parameters of the various indicators input by the user, a service module is generated and displayed in the unpublished area.

[0258] As an optional implementation manner, the indicator parameter includes a service type, and one service type corresponds to one display mode; the processor 1900 is specifically configured to execute:

[0259] According to the display mode corresponding to the service type in the indicator parameter input by the user, the service module is displayed in the unpublished area in the display mode corresponding to the service type.

[0260] As an optional implementation manner, the processor 1900 is specifically configured to execute:

[0261] In response to a service adding operation by a user on the visual interface, displaying a service configuration interface according to a service type of a service corresponding to the service adding operation;

[0262] Among them, at least one indicator among the multiple indicators displayed on the service configuration interface corresponding to different service types is different.

[0263] As an optional implementation, the indicators include any one or more of the following:

[0264] Service name; service type; IP or domain name; port; path; interceptor; filter; version; auxiliary service; upstream service; downstream service; hidden service; auxiliary path; anonymous path; request method.

[0265] As an optional implementation manner, the processor 1900 is further configured to execute:

[0266] In response to a user dragging a designated service module to the unpublished area, controlling the service corresponding to the designated service module to switch from a running state to a non-running state, and deleting a gateway configuration parameter corresponding to the designated service module;

[0267] The designated service module is selected by the user from the service modules in the published area.

[0268] As an optional implementation manner, the processor 1900 is further configured to execute:

[0269] In response to a user's deletion operation on a service module in an unpublished area, configuration data corresponding to the service module is deleted, wherein the configuration data includes gateway configuration parameters.

[0270] As an optional implementation, before the visual interface displays the service module, the processor 1900 is further configured to execute:

[0271] In response to the user's custom configuration operation on the visualization interface, at least one of the number of areas, area name, area location, area display method, area size, service module displayed in the area, and service type of the service module displayed in the area in the visualization interface is configured accordingly.

[0272] As an optional implementation, the service module displayed on the visual interface is used to represent the service in the microservice architecture;

[0273] The gateway configuration is used to perform access control and management on services in the microservice architecture.

[0274] Based on the same inventive concept, the embodiment of the present disclosure also provides a gateway configuration device. Since the device is the device in the method in the embodiment of the present disclosure, and the principle of solving the problem by the device is similar to that of the method, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0275] As shown in FIG20 , the device includes:

[0276] A service display unit 2000 is configured to display service modules on a visual interface, wherein the visual interface includes a published area and an unpublished area. The published area is configured to display service modules of published services, and the unpublished area is configured to display service modules of unpublished services.

[0277] The gateway configuration unit 2001 is used to perform corresponding gateway configuration on the target service module and run the service corresponding to the target service module in response to the user's operation of dragging the target service module from the unpublished area to the published area, wherein the target service module is selected by the user from the service modules that are not running in the unpublished area.

[0278] As an optional implementation manner, the gateway configuration unit 2001 is specifically configured to:

[0279] According to the calling relationship between the target service module and the service modules in the published area, corresponding gateway configuration parameters are configured for the target service module.

[0280] As an optional implementation manner, the gateway configuration unit 2001 is specifically configured to determine the calling relationship between the target service module and the service module in the published area by any of the following methods:

[0281] Determine, based on the upstream service and / or downstream service in the indicator parameters of the target service module, the calling relationship between the target service module and the service module in the published area; wherein the upstream service is used to call the service corresponding to the target service module, and the downstream service is used to be called by the service corresponding to the target service module; or

[0282] In response to a manual connection operation performed by a user on the target service module and the service module in the published area, a calling relationship between the target service module and the service module in the published area is determined.

[0283] As an optional implementation manner, if the calling relationship between the target service module and the service module in the published area is determined based on the upstream service and / or downstream service in the indicator parameters of the target service module, the gateway configuration unit 2001 is further specifically used to:

[0284] The target service module and the service module having the calling relationship are connected to display the calling relationship.

[0285] As an optional implementation manner, the gateway configuration unit 2001 is further configured to:

[0286] A directional marker is displayed on the connection line, and the directional marker is used to indicate the flow direction of the service data of the service module in the calling relationship.

[0287] As an optional implementation manner, if the calling relationship between the target service module and the service module in the published area is determined in response to a user's manual connection operation on the target service module and the service module in the published area, the gateway configuration unit 2001 is further specifically configured to:

[0288] Display the connection corresponding to the manual connection operation;

[0289] The direction of the connection is determined according to the starting point and the end point of the manual connection operation, and the direction is displayed by a direction mark, which is used to indicate the flow direction of the service data of the service module in the call relationship.

[0290] As an optional implementation manner, after the directional indicator is displayed on the connection line, the directional indicator indicates that the service data is transmitted from the target service module to the first service module, and the gateway configuration unit 2001 is further configured to:

[0291] In response to the user dragging the directional marker to point to the second service module, the calling relationship between the target service module and the first service module is updated to the calling relationship between the target service module and the second service module.

[0292] As an optional implementation manner, the gateway configuration unit 2001 is further configured to:

[0293] The display mode of the connection line indicates the connection status between the target service module and the services corresponding to the service modules in the published area. Connections in different display modes indicate different connection statuses.

[0294] As an optional implementation, the service module in the published area includes a functional service module, which is used to provide corresponding functional services for the user; the published area includes a functional sub-area, which is used to display the functional service module; the display service unit 2000 is further specifically used to:

[0295] The hierarchy of functional services corresponding to the functional service modules is displayed; the functional service modules corresponding to functional services of different hierarchies are displayed in different functional areas of the functional sub-areas; functional services of higher hierarchies among functional services of different hierarchies can call functional services of lower hierarchies.

[0296] As an optional implementation manner, the display service unit 2000 is further configured to:

[0297] In response to a user dragging a designated service module from the functional sub-area to the unreleased area, adaptively adjusting the hierarchy of the functional services corresponding to the functional service modules in the functional sub-area; the designated service module is selected by the user from the functional service modules in the functional sub-area; or

[0298] In response to a user dragging a target service module from an unreleased area to the functional sub-area, the hierarchy of the functional service corresponding to the functional service module in the functional sub-area is adaptively adjusted; wherein the target service module is a functional service module in the unreleased area.

[0299] As an optional implementation manner, the display service unit 2000 is specifically configured to:

[0300] The level of the functional service corresponding to the functional service module is adaptively adjusted according to whether there is an upstream functional service for the functional service corresponding to the functional service module, and the maximum level of the upstream functional service when there is an upstream functional service; wherein the upstream functional service is used to call the functional service corresponding to the functional service module.

[0301] As an optional implementation manner, the display service unit 2000 is specifically configured to:

[0302] If the functional service corresponding to the functional service module does not have an upstream functional service, determining that the level of the functional service corresponding to the functional service module is the maximum level; or

[0303] If the functional service corresponding to the functional service module has an upstream functional service, the level of the functional service corresponding to the functional service module is determined according to the maximum level of the upstream functional service.

[0304] As an optional implementation manner, the service module includes any one or more of the following service types:

[0305] Functional service module, which represents the functional service that provides functions for the user object;

[0306] Anonymous service module, representing an anonymous service that provides functions for functional services. The anonymous service does not require permission authentication when accessing the functional services;

[0307] Auxiliary service module, which represents the auxiliary service that provides functions for functional services;

[0308] The stealth service module represents a stealth service that provides functionality for the functional service and is not visible to the outside world.

[0309] The gateway service module manages all services except itself.

[0310] As an optional implementation manner, the display service unit 2000 is further configured to:

[0311] On the visual interface, at least one of the following information is displayed: the service name, service type, operating status, and gateway configuration parameters of the service corresponding to the service module; wherein the service type is determined according to the function provided by the service; and the operating status indicates the load balancing status of the service.

[0312] As an optional implementation,

[0313] If the running status of the service corresponding to the service module is displayed, different running statuses are displayed in different ways, and the displayed running status is used to prompt the user to reasonably allocate hardware resources.

[0314] As an optional implementation manner, the display service unit 2000 is further configured to:

[0315] The published area and the unpublished area are displayed in different ways;

[0316] The display manner of the service module in the unpublished area is determined according to the service type of the service module, and service modules of different service types are displayed in different manners in the unpublished area.

[0317] As an optional implementation manner, the published area includes multiple sub-areas, and the sub-areas include functional sub-areas; the display service unit 2000 is further configured to:

[0318] Each sub-area is used to display service modules of the same service type; different sub-areas are used to display service modules of different service types; and different sub-areas have different display modes.

[0319] As an optional implementation manner, in response to a user dragging a target service module from an unpublished area to a published area, the display service unit 2000 is further configured to:

[0320] According to the service type of the target service module, a sub-area of ​​the published area having the same service type as the target service module is activated to prompt the user to drag the target service module to the activated sub-area.

[0321] As an optional implementation manner, the display service unit 2000 is further configured to:

[0322] In response to the user's service adding operation on the visual interface, a service configuration interface is displayed, wherein the service configuration interface is used to display various indicators of the service;

[0323] In response to the indicator parameters of the various indicators input by the user, a service module is generated and displayed in the unpublished area.

[0324] As an optional implementation, the indicator parameter includes a service type, and one service type corresponds to one display mode;

[0325] According to the display mode corresponding to the service type in the indicator parameter input by the user, the service module is displayed in the unpublished area in the display mode corresponding to the service type.

[0326] As an optional implementation manner, the display service unit 2000 is further configured to:

[0327] In response to a service adding operation by a user on the visual interface, displaying a service configuration interface according to a service type of a service corresponding to the service adding operation;

[0328] Among them, at least one indicator among the multiple indicators displayed on the service configuration interface corresponding to different service types is different.

[0329] As an optional implementation, the indicators include any one or more of the following:

[0330] Service name; service type; IP or domain name; port; path; interceptor; filter; version; auxiliary service; upstream service; downstream service; hidden service; auxiliary path; anonymous path; request method.

[0331] As an optional implementation manner, the gateway configuration unit 2001 is further configured to:

[0332] In response to a user dragging a designated service module to the unpublished area, controlling the service corresponding to the designated service module to switch from a running state to a non-running state, and deleting a gateway configuration parameter corresponding to the designated service module;

[0333] The designated service module is selected by the user from the service modules in the published area.

[0334] As an optional implementation manner, the gateway configuration unit 2001 is further configured to:

[0335] In response to a user's deletion operation on a service module in an unpublished area, configuration data corresponding to the service module is deleted, wherein the configuration data includes gateway configuration parameters.

[0336] As an optional implementation manner, before the visual interface displays the service module, the gateway configuration unit 2001 is further configured to:

[0337] In response to the user's custom configuration operation on the visualization interface, at least one of the number of areas, area name, area location, area display method, area size, service module displayed in the area, and service type of the service module displayed in the area in the visualization interface is configured accordingly.

[0338] As an optional implementation, the service module displayed on the visual interface is used to represent the service in the microservice architecture;

[0339] The gateway configuration is used to perform access control and management on services in the microservice architecture.

[0340] Based on the same inventive concept, embodiments of the present disclosure provide a computer storage medium comprising computer program code. When executed on a computer, the computer program code causes the computer to execute any of the gateway configuration methods discussed above. Because the principles underlying the problems solved by the computer storage medium are similar to those of the gateway configuration method, the implementation of the computer storage medium can be referenced to the implementation of the method, and any repetitions will be omitted.

[0341] In a specific implementation process, computer storage media may include: Universal Serial Bus Flash Drive (USB), mobile hard disk, Read-Only Memory (ROM), Random Access Memory (RAM), magnetic disk or optical disk, and other storage media that can store program code.

[0342] Based on the same inventive concept, embodiments of the present disclosure further provide a computer program product comprising computer program code that, when executed on a computer, causes the computer to execute any of the gateway configuration methods discussed above. Because the principles underlying the problems solved by the aforementioned computer program products are similar to those of the gateway configuration methods, the implementation of the aforementioned computer program products can be referenced to the implementation of the methods, and any repetitions will not be repeated.

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

[0344] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0345] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0346] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0347] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0348] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.

Claims

1. A gateway configuration method, wherein: The method includes: Displaying service modules on a visual interface, wherein the visual interface includes a published area and an unpublished area, wherein the published area is used to display service modules of published services, and the unpublished area is used to display service modules of unpublished services; In response to a user's operation of dragging a target service module from an unpublished area to a published area, a corresponding gateway configuration is performed on the target service module, and a service corresponding to the target service module is run, wherein the target service module is selected by the user from service modules that are not running in the unpublished area.

2. The method according to claim 1, wherein The performing corresponding gateway configuration on the target service module includes: According to the calling relationship between the target service module and the service modules in the published area, corresponding gateway configuration parameters are configured for the target service module.

3. The method according to claim 2, wherein: Determine the calling relationship between the target service module and the service module in the published area by any of the following methods: Determine, based on the upstream service and / or downstream service in the indicator parameters of the target service module, the calling relationship between the target service module and the service module in the published area; wherein the upstream service is used to call the service corresponding to the target service module, and the downstream service is used to be called by the service corresponding to the target service module; or In response to a manual connection operation performed by a user on the target service module and the service module in the published area, a calling relationship between the target service module and the service module in the published area is determined.

4. The method according to claim 3, wherein: If the calling relationship between the target service module and the service modules in the published area is determined based on the upstream service and / or downstream service in the indicator parameters of the target service module, the method further includes: Connect the target service module and the service module with the calling relationship to display the Describe the calling relationship.

5. The method according to claim 4, wherein Also includes: A directional marker is displayed on the connection line, and the directional marker is used to indicate the flow direction of the service data of the service module in the calling relationship.

6. The method according to claim 3, wherein: If the calling relationship between the target service module and the service module in the published area is determined in response to a manual connection operation of the user on the target service module and the service module in the published area, the method further includes: Display the connection corresponding to the manual connection operation; The direction of the connection is determined according to the starting point and the end point of the manual connection operation, and the direction is displayed by a direction mark, which is used to indicate the flow direction of the service data of the service module in the call relationship.

7. The method according to claim 5 or 6, wherein: After a directional indicator is displayed on the connection line, the directional indicator indicates that the service data is transmitted from the target service module to the first service module, further comprising: In response to the user dragging the directional marker to point to the second service module, the calling relationship between the target service module and the first service module is updated to the calling relationship between the target service module and the second service module.

8. The method according to claim 4 or 6, wherein: Also includes: The display mode of the connection line indicates the connection status between the target service module and the service modules in the published area. The lines displayed in different ways represent different connection states.

9. The method according to any one of claims 1 to 6, wherein: The service module in the published area includes a function service module, which is used to provide corresponding function services for the user; the published area includes a function sub-area, which is used to display the function service module; and further includes: Display the level of the functional service corresponding to the functional service module; wherein the functional service modules corresponding to functional services of different levels are displayed in different functional areas in the functional sub-area; different levels Among the functional services at different levels, the functional services at higher levels can call the functional services at lower levels.

10. The method according to claim 9, wherein: Also includes: In response to a user's operation of dragging a designated service module from the functional sub-area to the unreleased area, adaptively adjusting the level of the functional service corresponding to the functional service module in the functional sub-area; The designated service module is selected by the user from the functional service modules in the functional sub-area; or In response to a user dragging a target service module from the unreleased area to the functional sub-area, adaptively adjusting the level of the functional service corresponding to the functional service module in the functional sub-area; The target service module is a functional service module in the unreleased area.

11. The method according to claim 10, wherein: Adaptively adjusting the level of the functional service corresponding to the functional service module in the functional sub-area includes: The level of the functional service corresponding to the functional service module is adaptively adjusted according to whether there is an upstream functional service for the functional service corresponding to the functional service module, and the maximum level of the upstream functional service when there is an upstream functional service; wherein the upstream functional service is used to call the functional service corresponding to the functional service module.

12. The method according to claim 11, wherein The adaptively adjusting the level of the functional service corresponding to the functional service module includes: If the functional service corresponding to the functional service module does not have an upstream functional service, determining that the level of the functional service corresponding to the functional service module is the maximum level; or If the functional service corresponding to the functional service module has an upstream functional service, the level of the functional service corresponding to the functional service module is determined according to the maximum level of the upstream functional service.

13. The method according to any one of claims 1 to 6 and 10 to 12, wherein: The service modules include any one or more of the following service types: Functional service module, which represents the functional service that provides functions for the user object; Anonymous service module, representing an anonymous service that provides functions for functional services. The anonymous service does not require permission authentication when accessing the functional services; Auxiliary service module, which represents the auxiliary service that provides functions for functional services; The stealth service module represents a stealth service that provides functionality for the functional service and is not visible to the outside world. The gateway service module manages all services except itself.

14. The method according to any one of claims 1 to 6 and 10 to 12, wherein: Also includes: On the visual interface, at least one of the following information is displayed: the service name, service type, operating status, and gateway configuration parameters of the service corresponding to the service module; wherein the service type is determined according to the function provided by the service; and the operating status indicates the load balancing status of the service.

15. The method according to claim 14, wherein If the running status of the service corresponding to the service module is displayed, different running statuses are displayed in different ways, and the displayed running status is used to prompt the user to reasonably allocate hardware resources.

16. The method according to any one of claims 1 to 6 and 10 to 12, wherein: Also includes: The published area and the unpublished area are displayed in different ways; The display manner of the service module in the unpublished area is determined according to the service type of the service module, and service modules of different service types are displayed in different manners in the unpublished area.

17. The method according to any one of claims 1 to 6 and 10 to 12, wherein: The released area includes multiple sub-areas, each of which includes a functional sub-area; and further includes: Each sub-area is used to display service modules of the same service type; different sub-areas are used to display service modules of different service types; and different sub-areas have different display modes.

18. The method according to claim 17, wherein In response to a user dragging a target service module from an unpublished area to a published area, the method further includes: According to the service type of the target service module, a sub-area of ​​the published area having the same service type as the target service module is activated to prompt the user to drag the target service module to the activated sub-area.

19. The method according to any one of claims 1 to 6 and 10 to 12, wherein: Also includes: In response to the user's service adding operation on the visual interface, a service configuration interface is displayed, wherein the service configuration interface is used to display various indicators of the service; In response to the indicator parameters of multiple indicators input by the user, a service module is generated and area to display.

20. The method according to claim 19, wherein The indicator parameters include service type, and one service type corresponds to one display mode; According to the display mode corresponding to the service type in the indicator parameter input by the user, the service module is displayed in the unpublished area in the display mode corresponding to the service type.

21. The method according to claim 19, wherein In response to the user's service addition operation on the visual interface, a service configuration interface is displayed, including: In response to a service adding operation by a user on the visual interface, displaying a service configuration interface according to a service type of a service corresponding to the service adding operation; Among them, at least one indicator among the multiple indicators displayed on the service configuration interface corresponding to different service types is different.

22. The method according to claim 19, wherein The indicators include any one or more of the following: Service name; service type; IP or domain name; port; path; interceptor; filter; version; auxiliary service; upstream service; downstream service; hidden service; auxiliary path; anonymous path; request method.

23. The method according to any one of claims 1 to 6 and 10 to 12, wherein: Also includes: In response to a user dragging a designated service module to the unpublished area, controlling the service corresponding to the designated service module to switch from a running state to a non-running state, and deleting a gateway configuration parameter corresponding to the designated service module; The designated service module is selected by the user from the service modules in the published area.

24. The method according to any one of claims 1 to 6 and 10 to 12, wherein: Also includes: In response to a user's deletion operation on a service module in an unpublished area, configuration data corresponding to the service module is deleted, wherein the configuration data includes gateway configuration parameters.

25. The method according to any one of claims 1 to 6 and 10 to 12, wherein: Before the service module is displayed on the visual interface, the method further includes: In response to the user's custom configuration operation on the visual interface, the area in the visual interface is At least one of the number of domains, area name, area location, area display mode, area size, service module displayed in the area, and service type of the service module displayed in the area is configured accordingly.

26. The method according to any one of claims 1 to 6 and 10 to 12, wherein: The service modules displayed on the visual interface are used to represent services in the microservice architecture; The gateway configuration is used to perform access control and management on services in the microservice architecture.

27. An electronic device, wherein: The electronic device includes a processor and a memory, wherein the memory is used to store a program executable by the processor, and the processor is used to read the program in the memory and execute the steps of any one of the methods of claims 1 to 26.

28. A computer storage medium having a computer program stored thereon, wherein: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 26 are implemented.

Images