Distributed geographic information systems, service processing methods, computer systems, and readable storage media

Abstract

The application relates to the technical field of computer systems, in particular to a distributed geographic information system, a service processing method, a computer system and a readable storage medium. A service unified management platform including service governance capability and life cycle management function is extended on the basis of a registration center, protection mechanisms such as flow limiting, fusing, response rewriting and the like are added to enhance the service governance capability of the system, and approval and full-link tracking capability are added to fill the blank of life cycle management in the system, so that the applicability of the distributed geographic information system in different scenes is improved. The application aims to solve the problem of how to improve the applicability of the distributed geographic information system in different scenes.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer systems, and particularly relates to a distributed geographic information system, a service processing method, a computer system and a readable storage medium. BACKGROUND

[0002] The distributed GIS (Geographic Information System) service architecture refers to a GIS service architecture realized based on static configuration or a basic registration center, and a typical implementation manner is that after a consumer directly configures an IP / port of a service provider, a load of a server is regulated by a system management tool.

[0003] The strong consistency of the traditional Zookeeper architecture requires that a majority of nodes write successfully, and in a high-frequency service registration scene, this can cause a sharp drop in throughput, therefore, for the high-frequency service registration scene, the Nacos architecture is currently commonly used, and when the Nacos architecture receives a registration request, only one node needs to be successful, and then through an asynchronous replication cluster, a consumer can obtain a latest list, so as to improve concurrent capability.

[0004] However, the traditional Nacos architecture only provides registration, discovery and configuration functions, and the applicant found that the native capability of the traditional Nacos architecture has certain limitations in the process of conceiving and implementing the present application: in the process of service going online, service changing and service going offline, the traditional Nacos architecture lacks service management capability due to the lack of protection mechanisms such as flow limiting and fusing, in addition, the lack of approval and link tracking capability also causes the life cycle management of the system to be blank, and further causes the system of the architecture to have the defect of insufficient applicability when involving sensitive data management.

[0005] Therefore, the present application aims to propose a new distributed geographic information system to improve the applicability of the system in different scenes. SUMMARY

[0006] The main purpose of the present application is to provide a distributed geographic information system, a service processing method, a computer system and a readable storage medium, and aims to solve the problem of how to improve the applicability of the distributed geographic information system in different scenes.

[0007] To achieve the above purpose, the distributed geographic information system provided by the present application comprises a registration center, and further comprises:

[0008] The service provider includes a unified service management platform. In response to the registration information issued by the registration center, the unified service management platform performs at least one of the following operations: offline, update, rate limiting and circuit breaking response rewrite configuration, and online. After the operation is completed, the service information generated is synchronized to the service gateway. The unified service management platform triggers a service status change after synchronizing the approval status to the metadata database of the registration center each time service information is generated.

[0009] Service users respond to the input target service capability selection command and obtain the authorization license corresponding to the target service capability when the service status changes to the approval authorization status from the registration center through the service gateway;

[0010] The service gateway is used to send the service call information associated with the service request to the link tracing platform after receiving a service request from a service user.

[0011] The call tracing platform is used to store the call chain and system logs of the service call information.

[0012] Optionally, the unified service management platform further includes:

[0013] The dynamic rate limiting and circuit breaker configuration module includes multiple dynamic rate limiting rules, which are used to perform service circuit breaker operations when the load status of the system is detected to meet the dynamic rate limiting rules.

[0014] Optionally, the service provider may further include:

[0015] An online debugging module is used to test the connectivity of the target service capabilities.

[0016] Optionally, the unified service management platform further includes:

[0017] The canary release module is used to send the updated service capabilities to a target proportion of service users after detecting that there is a service capability update with a subscription identifier, wherein the target proportion increases with the increase of the update time of the service capability.

[0018] Optionally, the distributed geographic information system further includes:

[0019] The multi-dimensional statistics module is used to analyze at least one of the following: total service data for single users and the system, number of service catalogs at the system level, service ranking data for single users and the system, service call data for single users and the system, and service performance analysis data.

[0020] Furthermore, to achieve the above objectives, this application also provides a service processing method applied to a unified service management platform in a distributed geographic information system as described above, the method comprising the following steps:

[0021] In response to the registration information issued by the registration center, perform at least one of the following operations: offline, update, rate limiting circuit breaker rewrite configuration and online, generate service information and synchronize the approval result identifier associated with the service information to the metadata database of the registration center to trigger the service status change of the registration center;

[0022] The service information and registration information are synchronized to the service gateway.

[0023] Optionally, the current-limiting circuit breaker rewrite configuration includes the following steps:

[0024] Detect whether the service capabilities associated with the registration information are offline;

[0025] If so, respond to at least one of the input rate limiting command, circuit breaker command, and rewrite command, and generate the service information corresponding to the command;

[0026] The service information is sent to the registration center.

[0027] Optionally, the unified service management platform further includes a dynamic rate limiting and circuit breaker configuration module, which includes the following steps when executing a circuit breaker command:

[0028] The system divides the service area into grids of preset size and creates an independent fuse for each service area;

[0029] A data capture instruction for the service area is sent to the service gateway at preset intervals, so that when the service gateway receives the data capture instruction, it obtains the geographical coordinates corresponding to the service area from the registration center and sends them to the unified service management platform.

[0030] Determine the risk score associated with the geographic coordinates;

[0031] Based on the range of the risk score, the target circuit breaker strategy corresponding to the service area is determined. The target circuit breaker strategy includes a full circuit breaker strategy, a partial circuit breaker strategy, and an early warning strategy.

[0032] In addition, to achieve the above objectives, this application also provides a computer system comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the service processing method as described in any of the preceding claims.

[0033] In addition, to achieve the above objectives, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the service processing method as described in any of the preceding claims.

[0034] This application has at least the following beneficial effects:

[0035] Based on the registration center, a unified service management platform has been expanded to include service governance capabilities and lifecycle management functions. Protection mechanisms such as rate limiting, circuit breaking, and response rewriting have been added to enhance the system's service governance capabilities, and approval and end-to-end tracking capabilities have been added to fill the gaps in lifecycle management in the system, thereby improving the applicability of the distributed geographic information system in different scenarios. Attached Figure Description

[0036] Figure 1 This is a schematic diagram of the architecture of the distributed geographic information system involved in the embodiments of this application;

[0037] Figure 2 This is a schematic diagram of the architecture of the dynamic current limiting and circuit breaker configuration module involved in the embodiments of this application;

[0038] Figure 3 This is a schematic diagram of the architecture of the online debugging module involved in the embodiments of this application;

[0039] Figure 4 This is a schematic diagram of the architecture of the grayscale release module involved in the embodiments of this application;

[0040] Figure 5 This is a schematic diagram of the architecture of the multi-dimensional statistical data module involved in an embodiment of this application;

[0041] Figure 6 This is a flowchart of a service processing method involved in an embodiment of this application;

[0042] Figure 7 This is a schematic diagram of the hardware operating environment of the computer system involved in the embodiments of this application.

[0043] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0044] To better understand the above technical solutions, exemplary embodiments of this disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art.

[0045] First Embodiment

[0046] Reference Figure 1The diagram shows the architecture of a distributed geographic information system. The distributed geographic information system includes a registration center 100. In this embodiment, the registration center is also called a distributed service registration center. As a repository for service registration, it records and manages the metadata of GIS services. It not only provides basic service registration and discovery functions, but also has advanced features such as dynamic configuration management, high availability and cluster deployment, health checks and load balancing, namespace and group management, and advanced configuration scenarios.

[0047] In some alternative implementations, the registry center 100 may be deployed using an existing Nacos distributed registry center or a Consul-based distributed registry center; this embodiment does not impose any limitations.

[0048] The distributed geographic information system also includes:

[0049] Service provider 200 includes a unified service management platform 201. In response to the registration information issued by the registration center, the unified service management platform 201 performs at least one of the following operations: offline, update, rate limiting and circuit breaking response rewrite configuration, and online. After the operation is completed, it synchronizes the service information generated to the service gateway 400. The unified service management platform 201 triggers a service status change after synchronizing the approval status to the metadata of the registration center 100 each time service information is generated.

[0050] Specifically, rate limiting, circuit breaking, and response rewriting in the platform can be input through the service provider or pre-configured by the service provider. When the execution policy is met, one or more of the following operations will be automatically performed: rate limiting, circuit breaking, and response rewriting. Each execution policy generates a unique configuration ID form data for storage.

[0051] In some optional implementations, the rate limiting strategy may include a rate limiting type, a maximum number of requests per second, and a maximum number of concurrent connections. When it is detected that the rate limiting type of the service matches the target rate limiting type, and the maximum number of requests per second of the target rate limiting type is greater than a preset request threshold, and the maximum number of concurrent connections is greater than a preset concurrency threshold, the rate limiting operation is triggered.

[0052] In some optional implementations, the circuit breaker strategy may include an error rate and a trigger duration. When the error rate of a service is detected to be greater than a preset error rate threshold and the trigger duration is greater than the duration threshold, the circuit breaker operation is triggered.

[0053] In some optional implementations, the rule configuration for responding to rewrite operations may include HTTP status code mapping, sensitive field masking, and data format conversion, as shown in Table 1 below:

[0054] Table 1. Example of Response Rewrite Operation Configuration

[0055]

[0056] Finally, the platform converts the form data into the corresponding settings in the registration center, stores them in the metadata database table, and saves them in the corresponding key format in the metadata database table, thus completing the rewrite configuration of the rate limiting and circuit breaker response.

[0057] Furthermore, in order to address issues such as fragmented service capabilities, ambiguous service permission boundaries, inefficient service application and approval processes, difficulties in connecting service users with 300, redundancy and complexity of various service capabilities, and lack of unified management, the distributed geographic information system configures a unified service management platform 201 among service providers.

[0058] Service provider 200 refers to a system, module, or capability interface that can provide services to the outside world, such as an algorithm model orchestrated by the algorithm model orchestration subsystem, or an interface that can provide map retrieval capabilities. Upon startup, the service provider can automatically or manually register its request address and data format information with the registration center; in this embodiment, it can be understood as a client of the service delivery object.

[0059] The unified service management platform 201 refers to the ability to manage its own externally provided service capabilities, including online and offline management; consumers can search for and apply for the services they need and obtain service usage licenses. As a consumer of the registry center, the unified service management platform automatically discovers registered services by integrating the development toolkit (SDK) provided by the registry center or accessing the OpenAPI specifications exposed by the registry center.

[0060] The registration center 100 proactively pushes registration information, including but not limited to the service provider's IP address, port, health status, and weight, to the unified service management platform 201. The unified service management platform, acting as an event-driven consumer, listens for and processes change notifications from the registration center in real time.

[0061] In this embodiment, the unified service management platform (hereinafter referred to as the platform) mainly provides two functions: providing service governance and lifecycle management.

[0062] Service governance, as one of the innovative aspects of this solution, is achieved through the execution strategy following the implementation of rate limiting, circuit breaking, and rewriting configurations by the platform. This ensures that there are governance measures in place for situations such as excessive load and data errors that may occur in high-throughput scenarios. Specifically, the platform first checks whether the service requiring rate limiting, circuit breaking, and rewriting configuration operations is offline to ensure that the rate limiting, circuit breaking, and rewriting configuration operations for that service do not affect service users.

[0063] Regarding lifecycle management, this mechanism is another innovation in this solution, which integrates the two major capabilities of approval process and end-to-end tracking throughout the entire lifecycle management of GIS services.

[0064] Regarding the technical implementation of the approval process, the unified service management platform synchronizes the approval status to the metadata of the registration center each time service information is generated, and then triggers a service status change.

[0065] Specifically, when a service provider submits a service launch application, the platform generates an approval task, and the service status is marked as pending approval. After the administrator (who can also be classified as a service provider) with higher privileges than the service provider who submitted the service launch application approves the application, the platform calls the OpenAPI of the registry center to update the extended fields of the service metadata. The registry center monitors the metadata change and triggers the built-in state machine to update the service status.

[0066] It should be noted that, unlike traditional independent approval systems, this embodiment embeds the business approval status into the infrastructure layer metadata.

[0067] For the technical implementation of end-to-end tracing, probes are implanted at key nodes of service calls to generate globally unique tracing IDs and record detailed information about the service calls, including but not limited to timestamps, service IDs, operation types, GIS coordinates, etc., forming a complete call chain. This mechanism runs through the four lifecycle stages of the GIS service: launch, consumption, update, and lower limit, which is end-to-end tracing.

[0068] Specifically, this is achieved by setting up a spatiotemporal coordinate axis in the Link Tracing Platform 500. The spatiotemporal coordinate axis uses the GIS service coordinate range as the spatial axis and the timestamp sequence from registration to offline as the time axis.

[0069] After the unified service management platform performs at least one of the following operations: offline, update, rate limiting and circuit breaker response rewrite configuration, and online, the registration center 100 records the operation information and generates a corresponding timestamp. The operation information, along with the timestamp, is forwarded to the tracing platform 500 through the service gateway 400. The tracing platform 500 matches the registration request associated with the operation information, finds the geospatial coordinates corresponding to the time the registration request was generated, and then associates the operation information, timestamp, and geospatial coordinates to generate a globally unique tracing ID, which is stored in the storage layer of the tracing platform 500. When needed, the operation content, generation time, and generation address of the service provider's operation can be found through this tracing ID.

[0070] Service user 300 responds to the input target service capability selection command and obtains the authorization license corresponding to the target service capability when the service status changes to the approval authorization status from the registration center 100 through the service gateway 400.

[0071] In this embodiment, service user 300 refers to an application or client that needs to apply for other capabilities. The consumer selects the required service capabilities in the unified service management platform 201, and after authorization, obtains permission to invoke the requested service capabilities.

[0072] As a user, the user inputs the instruction to select the desired service capability through the service user 300, i.e. the target service capability. The service user 300 needs to review whether the instruction is permitted and obtain the metadata of the authorization license corresponding to the target service capability when the service status changes to the approval authorization status from the registration center 100. Once the authorization license is obtained, the instruction is deemed to be allowed to be executed.

[0073] Understandably, execution is not permitted if no authorization is obtained, or if metadata indicating a change in service status to non-approved authorization is obtained.

[0074] In some optional implementations, the service user 300 calls the API of the registration center 100 to obtain the approval status metadata of the service. If the service status of the target service capability contains an identifier that indicates "the service has been approved and authorized", the registration center 100 generates an authorization license.

[0075] Note that the license should include a cryptographic token and an expiration date. The cryptographic token should include the service ID and the user ID.

[0076] It is worth noting that in traditional GIS solutions, service permissions are hard-coded in configuration files. The solution in this embodiment creatively proposes real-time linkage of permission status with the registry center's metadata.

[0077] Service gateway 400 is used to send the service call information associated with the service request to the link tracing platform 500 after receiving a service request from service user 300.

[0078] The link tracing platform 500 is used to store the call chain and system logs of the service call information.

[0079] In this embodiment, the online debugging and instance invocation operations of the service by the service user 300 are all carried out through the service gateway 400. After receiving the service request, the service gateway 400 sends the relevant service invocation information to the link tracing platform 500 and records the call link and system log of the service invocation information.

[0080] The main function of the service gateway 400 in this embodiment is message forwarding.

[0081] Specifically, when a service request passes through the gateway, key information in the service request is automatically captured and sent to the distributed tracing platform. In some alternative implementations, the gateway sends data in an asynchronous, non-blocking manner.

[0082] In this embodiment, the link tracing platform 500 includes a three-layer processing architecture: a data acquisition layer, a storage layer, and an analysis layer. The data acquisition layer is used to receive network management data, the storage layer is used to call link persistence, and the analysis layer is used for visualization analysis.

[0083] In the technical solution provided in this embodiment, a unified service management platform is extended on the basis of the registration center, including service governance capabilities and lifecycle management functions. Protection mechanisms such as rate limiting, circuit breaking, and response rewriting are added to enhance the system's service governance capabilities, and approval and full-link tracing capabilities are added to fill the gaps in lifecycle management in the system, thereby improving the applicability of the system in different scenarios.

[0084] Second Embodiment

[0085] Based on the first embodiment, referring to Figure 2 In this embodiment, the unified service management platform 201 further includes:

[0086] The dynamic current limiting and circuit breaker configuration module includes multiple dynamic current limiting rules, which are used to perform current limiting and / or circuit breaker operations when the load state of the system is detected to meet the dynamic current limiting rules.

[0087] Third Embodiment

[0088] Based on any embodiment, refer to Figure 3 In this embodiment, the distributed geographic information system also supports online connectivity testing, and the service provider 200 further includes:

[0089] The online debugging module 202 is used to test the connectivity of the target service capabilities.

[0090] In this embodiment, the online debugging module 202 built into the service provider can realize the dual functions of service connectivity verification and capability testing.

[0091] Specifically, the online debugging module 202 can provide a test entry point for users to input test commands, which may include, but are not limited to, connectivity tests.

[0092] In some alternative implementations, connectivity testing can be defined based on TCP handshake time. The current connectivity status of the target service capability can be determined as high latency, medium latency, or low latency based on the range of the TCP handshake time value obtained from the test.

[0093] Fourth embodiment

[0094] Based on any embodiment, refer to Figure 4 In this embodiment, the distributed geographic information system also supports phased canary releases during service updates, and the unified service management platform 201 further includes:

[0095] The gray-scale release module 2012 is used to send the updated service capabilities to a target proportion of service users after detecting that there is a service capability update with a subscription identifier, wherein the target proportion increases with the increase of the update time of the service capability.

[0096] Specifically, after a user submits a new version through service provider 200 and selects the canary release option, service provider 200 marks it in the update description and synchronizes it to the corresponding metadata of the record in the registry center 100, adding an updated subscription identifier field to the metadata. The unified service management platform 201 initializes the initially sent target ratio, selects target users who meet the target ratio from all service users 300 ports that have subscribed to the service, and sends the updated subscription content to the target users.

[0097] In some optional implementations, the grayscale rule configurations are shown in Table 2 below:

[0098] Table 2. Example of Grayscale Rule Configuration

[0099]

[0100] Fifth embodiment

[0101] Based on any embodiment, refer to Figure 5 In this embodiment, the distributed geographic information system also supports multi-dimensional statistics. The distributed geographic information system further includes:

[0102] The multi-dimensional statistical data module 600 includes at least one of the following: total service data for single user and system dimensions, system-level service catalog quantity data, service ranking data for single user and system dimensions, service call data for single user and system dimensions, and service performance analysis data.

[0103] The total service data for a single user and the system level refers to the total service metrics recorded for each user and at the system level within the module, including but not limited to the number of active services, the number of offline services, and the service dependency graph. It is primarily used to identify zombie services in the system (such as services that have not been called for 90 days) and optimize resource allocation.

[0104] System-level service catalog quantity data refers to the statistical distribution of various GIS service catalogs, including but not limited to the number of spatial analysis services, data conversion services, and visualization services. It is primarily used to statistically analyze the service categories of subscribed services within the system and to identify which service types are more popular among users.

[0105] Service ranking data at the individual user and system levels refers to the ranking of each user's evaluation of the subscribed services, including but not limited to the number of subscriptions and positive review rate. It is mainly used to analyze the popularity of specific subscription services.

[0106] Service call data at the single-user and system dimensions refers to the spatiotemporal distribution characteristics of service usage, including but not limited to call time distribution, geographic coordinate distribution, and call frequency trends. It is primarily used to detect abnormal areas in the system, such as outputting geographic coordinates with a call frequency >30% within the last 10 minutes.

[0107] Service performance analysis data includes, but is not limited to, average response time, error type distribution, and resource consumption rate, and is mainly used to detect system performance.

[0108] Furthermore, as an implementation scheme, Figure 6 A flowchart illustrating the service processing method of a unified service management platform in a distributed geographic information system designed for the embodiments of this application, the method comprising the following steps:

[0109] Step S10: In response to the registration information issued by the registration center, perform at least one of the following operations: offline, update, rate limiting circuit breaker rewrite configuration and online, generate service information and synchronize the approval result identifier associated with the service information to the metadata database of the registration center to trigger the service status change of the registration center;

[0110] Step S20: Synchronize the service information and the registration information to the service gateway.

[0111] Furthermore, in some optional implementations, the current-limiting circuit breaker rewrite configuration includes the following steps:

[0112] Step S11: Detect whether the service capabilities associated with the registration information are offline;

[0113] Step S12: If yes, respond to at least one of the input rate limiting instruction, circuit breaker instruction, and rewrite instruction, and generate service information corresponding to the instruction;

[0114] Step S13: Send the service information to the registration center.

[0115] Furthermore, in some optional embodiments, the unified service management platform further includes a dynamic rate limiting and circuit breaking configuration module, which includes the following steps when executing a circuit breaking command:

[0116] Step S121: Divide the service area of ​​the system into grids of preset size, and create an independent fuse for each service area;

[0117] In this step, compared to traditional global circuit breaking, the system is divided into service areas by a grid of preset size, and an independent circuit breaker is created for each service area to achieve independent circuit breaking on a service area basis.

[0118] Step S122: Send a data capture instruction for the service area to the service gateway at preset intervals, so that when the service gateway receives the data capture instruction, it obtains the geographical coordinates corresponding to the service area from the registration center and sends them to the unified service management platform.

[0119] Next, the module periodically sends data capture instructions for each service region to the service gateway. In some implementations, this is preset to occur every 5 minutes. When the service gateway receives the data capture instruction, it obtains the geographic coordinates corresponding to the service region from the registry center and sends them to the unified service management platform.

[0120] Step S123: Determine the risk score associated with the geographic coordinates;

[0121] In this step, each service area corresponds to a risk score, which is correlated with geographic coordinates. The risk score of the service area is found by obtaining the geographic coordinates.

[0122] The risk score represents the probability that a circuit breaker-required event may occur in the service area. In some alternative implementations, the risk score is determined by error rate, disaster level, terrain complexity, and network quality.

[0123] Error rate refers to the proportion of failed requests out of the total requests within a service area, reflecting service reliability. Its data source is the request-response logs captured by the service gateway. Its value range is (0, 1).

[0124] The disaster level refers to the current severity of the disaster in the service area, and its data source is collected through the Link Tracking Platform 500 external extended meteorological or geological monitoring service API.

[0125] For example, the disaster level can be set to 0-5, where 0 represents no disaster and 5 represents the most severe, normalized to the interval [0,1].

[0126]

[0127] Terrain complexity refers to the degree of complexity of the terrain in the service area, which affects network transmission and service response. Its data source is the multi-dimensional statistical data module 600 external digital elevation model (DEM) used to collect elevation changes and calculate network coverage coefficients.

[0128] For example, its calculation expression can be found as follows:

[0129]

[0130] Network quality refers to the quantitative value of network connectivity reliability in the service area, and its data source is network probe packets collected in the service gateway over a historical period.

[0131] For example, network quality is calculated based on the number of successful probe identifiers in network probe packets over a historical period and the total number of probe packets. The calculation expression can be found here:

[0132]

[0133] The above indicators together form the basis for calculating the risk score. Each indicator is weighted and fused to calculate the final risk score.

[0134] The specific weights of each value in the risk score are not the focus of this embodiment.

[0135] Step S124: Based on the range of the risk score, determine the target circuit breaker strategy corresponding to the service area. The target circuit breaker strategy includes a full circuit breaker strategy, a partial circuit breaker strategy, and an early warning strategy.

[0136] A complete circuit breaker strategy refers to completely isolating the problematic area to ensure overall system stability. Optionally, this may include, but is not limited to: rejecting all new inbound requests, returning a standardized 503 response, automatically triggering disaster recovery plans (lifecycle management functions), physically isolating the failed server, and blocking the affected area via DNS routing.

[0137] Partial circuit breaker strategies refer to strategies that reduce system load while preserving core functionality. Optionally, these strategies may include, but are not limited to, limiting regional traffic to a baseline value, queuing asynchronous requests, and dynamically adjusting QPS thresholds.

[0138] Early warning strategies refer to strategies that prevent system crashes through resource optimization. Optionally, these strategies may include, but are not limited to: sending early warning notifications to the service provider, marking the service area as high priority, and increasing the data sampling frequency.

[0139] In some optional implementations, the risk score ranges from [0, 1]. When the risk score is in the range of [0, 0.4), the target circuit breaker strategy is an early warning strategy. When the risk score is in the range of [0.4, 0.8), the target circuit breaker strategy is a partial circuit breaker strategy. When the risk score is in the range of [0.8, 1], the target circuit breaker strategy is a complete circuit breaker strategy.

[0140] As one implementation scheme, Figure 7This is a schematic diagram of the hardware operating environment of the computer system involved in the embodiments of this application.

[0141] like Figure 7 As shown, the computer system may include: a processor 1001, such as a CPU; a memory 1005; a user interface 1003; a network interface 1004; and a communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0142] Those skilled in the art will understand that Figure 7 The computer system architecture shown does not constitute a limitation on the computer system and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0143] like Figure 7 As shown, the memory 1005, as a storage medium, may include an operating system, a network communication module, a user interface module, and computer programs. The operating system is a program that manages and controls the hardware and software resources of the computer system, as well as the operation of the computer programs and other software or programs.

[0144] exist Figure 7 In the computer system shown, the user interface 1003 is mainly used to connect to the terminal and communicate with the terminal; the network interface 1004 is mainly used to communicate with the backend server; and the processor 1001 can be used to call the computer program stored in the memory 1005.

[0145] In this embodiment, the computer system includes: a memory 1005, a processor 1001, and a computer program stored in the memory and executable on the processor, wherein:

[0146] When processor 1001 calls a computer program stored in memory 1005, it performs the following operations:

[0147] In response to the registration information issued by the registration center, perform at least one of the following operations: offline, update, rate limiting circuit breaker rewrite configuration and online, generate service information and synchronize the approval result identifier associated with the service information to the metadata database of the registration center to trigger the service status change of the registration center;

[0148] The service information and registration information are synchronized to the service gateway.

[0149] When processor 1001 calls a computer program stored in memory 1005, it performs the following operations:

[0150] Detect whether the service capabilities associated with the registration information are offline;

[0151] If so, respond to at least one of the input rate limiting command, circuit breaker command, and rewrite command, and generate the service information corresponding to the command;

[0152] The service information is sent to the registration center.

[0153] When processor 1001 calls a computer program stored in memory 1005, it performs the following operations:

[0154] The system divides the service area into grids of preset size and creates an independent fuse for each service area;

[0155] A data capture instruction for the service area is sent to the service gateway at preset intervals, so that when the service gateway receives the data capture instruction, it obtains the geographical coordinates corresponding to the service area from the registration center and sends them to the unified service management platform.

[0156] Determine the risk score associated with the geographic coordinates;

[0157] Based on the range of the risk score, the target circuit breaker strategy corresponding to the service area is determined. The target circuit breaker strategy includes a full circuit breaker strategy, a partial circuit breaker strategy, and an early warning strategy.

[0158] Furthermore, those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in a computer system to implement the process steps of the embodiments of the above methods.

[0159] Therefore, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the various steps of the service processing method described in the above embodiments.

[0160] The computer-readable storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0161] It should be noted that, since the storage medium provided in the embodiments of this application is the storage medium used to implement the methods of the embodiments of this application, those skilled in the art can understand the specific structure and variations of the storage medium based on the methods described in the embodiments of this application, and therefore will not be repeated here. All storage media used in the methods of the embodiments of this application fall within the scope of protection of this application.

[0162] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0163] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0164] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0165] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 Figure 1 The steps of the function specified in one or more boxes.

[0166] It should be noted that any reference signs placed between parentheses in the claims should not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. This application can be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

[0167] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0168] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A distributed geographic information system comprising a registry center, characterized in that, The distributed geographic information system further comprises: The service provider comprises a service unified management platform, which, in response to registration information issued by the registration center, executes at least one of the following operations: offline, update, flow limiting and fuse breaking response rewriting configuration and online, and then synchronizes service information generated after the operation to a service gateway, wherein the service unified management platform triggers service state change after synchronizing the approval state to the meta database of the registration center each time service information is generated; The service user responds to the input target service capability selection instruction and obtains the authorization permission corresponding to the target service capability when the service state change is the approval authorization state from the registration center through the service gateway; The service gateway is used for sending service call information associated with the service request to a link tracking platform after receiving the service request sent by the service user; The link tracking platform is used for storing the call link and system log of the service call information; The service unified management platform further comprises: The dynamic flow limiting and fuse breaking configuration module comprises a plurality of dynamic flow limiting rules, and is used for executing flow limiting and / or fuse breaking operation when detecting that the load state in the system meets the dynamic flow limiting rules; The dynamic flow limiting and fuse breaking configuration module comprises the following steps when executing the fuse breaking instruction: Divide the service area in the system into a grid with a preset size, and create an independent fuse breaker for each service area; Send a data capture instruction of the service area to the service gateway every preset period, so that when the service gateway receives the data capture instruction, it obtains the geographic coordinates corresponding to the service area from the registration center and sends them to the service unified management platform; Determine the risk score associated with the geographic coordinates; According to the interval of the risk score, determine the target fuse breaking strategy corresponding to the service area, which includes a complete fuse breaking strategy, a partial fuse breaking strategy and a warning strategy.

2. The distributed geographic information system of claim 1, wherein, The service provider further comprises: The online debugging module is used for testing the connectivity of the target service capability.

3. The distributed geographic information system of claim 1, wherein, The service unified management platform further comprises: The gray release module is used for sending the updated service capability to a target proportion of service users after detecting that there is a service capability update with a subscription identifier, wherein the target proportion increases with the increase of the update time length of the service capability.

4. The distributed geographic information system of claim 1, wherein, The distributed geographic information system further comprises: The multi-dimensional statistical data module is used for analyzing at least one of the following data: single user and system dimension service total data, system level service directory quantity data, single user and system dimension service ranking data, single user and system dimension service call condition data and service performance analysis data.

5. A service processing method applied to a service uniform management platform in the distributed geographic information system according to any one of claims 1 to 4, characterized in that, The method comprises the following steps: In response to the registration information issued by the registration center, at least one of the following operations is executed: offline, update, flow limiting and fuse breaking rewriting configuration and online, service information is generated, and the approval result identifier associated with the service information is synchronized to the meta database of the registration center to trigger service state change of the registration center; Synchronize the service information and the registration information to the service gateway.

6. The service processing method of claim 5, wherein, The flow limiting and fuse breaking rewriting configuration comprises the following steps: determining whether a service capability associated with the registration information is in an offline state; if yes, generating service information corresponding to at least one of the input throttling instruction, the fusing instruction and the rewriting instruction; sending the service information to the registration center.

7. A computer system, characterized by The computer system comprises a memory, a processor and a computer program stored on the memory and executable on the processor, and the computer program, when executed by the processor, implements the steps of the service processing method according to any one of claims 5 to 6.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program, when executed by the processor, implements the steps of the service processing method according to any one of claims 5 to 6.

Images