Application service management method, device and computer readable storage medium

Abstract

This application discloses an application service management method, device, and computer-readable storage medium, applied in the field of platform system construction. The method includes: when an integration interface receives an application service access instruction, determining an adaptation interface based on the platform architecture of the application service to be accessed; configuring the protocol stack corresponding to the application service to be accessed based on the adaptation interface; determining the required API of the application service to be accessed based on the access instruction, and determining the target server corresponding to the application service to be accessed based on the required API; generating a configuration file for the application service to be accessed based on the target server and the protocol stack; and executing the access action of the application service to be accessed based on the configuration file and the adaptation interface. This solves the technical problem of difficulty in achieving information interconnection and interoperability between cross-regional and cross-departmental systems in related technologies, and achieves the technical effect of connecting system platforms with different architectures and improving data governance.

Description

Technical Field

[0001] This application relates to the field of computer software and information service technology, and in particular to an application service management method, device and computer-readable storage medium. Background Technology

[0002] The government has built many online service windows, and almost every department has its own website and online service platform.

[0003] Some departments, based on their own management needs, have developed administrative approval systems tailored to their specific business operations, enabling many administrative matters to be applied for and processed online. However, these services are mostly conducted within the department, resulting in poor compatibility with other systems, inefficient information sharing, and difficulty in promoting cross-departmental cooperation, thus creating de facto information system silos.

[0004] However, due to differences in the construction time, platform architecture, technical routes, and data standards of business systems in different regions, it is difficult to achieve information interconnection and interoperability between regions and departments. Summary of the Invention

[0005] This application provides an application service management method, device, and computer-readable storage medium, which solves the technical problem of difficulty in achieving information interconnection and interoperability between cross-regional and cross-departmental areas in related technologies, and achieves the technical effect of connecting system platforms with different architectures and improving the level of data governance.

[0006] This application provides an application service management method, which includes:

[0007] When the integration interface receives an application service access instruction, it determines the appropriate interface based on the platform architecture of the application service to be accessed.

[0008] Configure the protocol stack corresponding to the application service to be accessed according to the adaptation interface;

[0009] Based on the access instruction, determine the required API of the application service to be accessed, and determine the target server corresponding to the application service to be accessed based on the required API.

[0010] Generate a configuration file for the application service to be accessed based on the target server and the protocol stack;

[0011] The access action of the application service to be accessed is performed based on the configuration file and the adaptation interface.

[0012] Optionally, the step of determining the required API of the application service to be accessed based on the access instruction, and determining the target server corresponding to the application service to be accessed based on the required API, includes:

[0013] The service type of the application service to be accessed and the required API are determined based on the access instruction.

[0014] The target server is determined based on the business type and the required API.

[0015] Based on a preset load balancing strategy, the target servers are divided into primary servers and backup servers according to a symmetrical structure.

[0016] The server identifiers of the symmetrical master server and the backup server are associated and stored.

[0017] Optionally, the step of generating the configuration file for the application service to be accessed based on the target server and the protocol stack includes:

[0018] Based on the data structure of the application service to be accessed, determine the business data model;

[0019] The data management rules for the application services to be accessed are determined based on the business data model.

[0020] The configuration file is generated based on the data management rules, the server identifier, and the protocol stack.

[0021] Optionally, after the step of performing the access action of the application service to be accessed based on the configuration file and the adaptation interface, the method further includes:

[0022] Obtain the target configuration file based on the received pending request, and determine the target server group;

[0023] Obtain the load status of the target server group, and determine the target server based on the load status and the load index of the request to be responded to;

[0024] The transport protocol is determined based on the target configuration file, and the request to be responded to is forwarded to the target server based on the transport protocol.

[0025] Control the target server to respond to the pending request.

[0026] Optionally, the step of controlling the target server to respond to the request to be responded to includes:

[0027] Obtain the data modification details corresponding to the request to be responded to, and record the data modification details to the write-ahead log;

[0028] Update the main database based on the data modification operations corresponding to the write-ahead log;

[0029] The write-ahead log is transmitted to the backup database, and the data modification operations are replayed on the backup database based on the time nodes.

[0030] Optionally, after the step of accessing the application service based on the configuration file and the adaptation interface, the method further includes:

[0031] Upon receiving an application service modification request, determine the configuration file to be modified corresponding to the modification request;

[0032] Analyze the modification request to determine the item to be modified and the corresponding modification value;

[0033] Based on the modified value, perform modification actions on the item to be modified in the configuration file to be modified.

[0034] Optionally, after the step of accessing the application service based on the configuration file and the adaptation interface, the method further includes:

[0035] Upon receiving an application service deletion request, determine the configuration file to be deleted corresponding to the deletion request;

[0036] Determine the server identifier and data field identifier contained in the configuration file to be deleted;

[0037] Release the server corresponding to the server identifier from its occupancy, and update the reference relationship of the data field corresponding to the data field identifier;

[0038] Perform a deletion action on the configuration file to be deleted.

[0039] Optionally, the step of releasing the server corresponding to the server identifier and updating the reference relationship of the data field corresponding to the data field identifier includes:

[0040] Update the server's usage status to idle;

[0041] Identify the single-reference fields and regular fields in the data fields;

[0042] Delete the single reference field and delete the reference relationship between the ordinary field and the data field identifier.

[0043] In addition, this application also proposes an application service management device, which includes a memory, a processor, and an application service management program stored in the memory and executable on the processor. When the processor executes the application service management program, it implements the steps of the application service management method described above.

[0044] In addition, this application also proposes a computer-readable storage medium storing an application service management program, which, when executed by a processor, implements the steps of the application service management method described above.

[0045] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0046] By employing a process that, upon receiving an application service access command at the integration interface, determines the appropriate interface based on the platform architecture of the application service to be accessed; configures the protocol stack corresponding to the application service based on the appropriate interface; determines the required API of the application service to be accessed based on the access information of the application service to be accessed, and determines the target server corresponding to the application service to be accessed based on the required API; generates a configuration file for the application service to be accessed based on the target server and the protocol stack; and executes the access action of the application service to be accessed based on the configuration file and the appropriate interface, this approach effectively solves the technical problem in related technologies where differences in the construction time, platform architecture, technical routes, and data standards of business systems in different regions make it difficult to achieve information interconnection and interoperability across regions and departments. This, in turn, achieves the technical effect of connecting system platforms with different architectures and improving data governance. Attached Figure Description

[0047] Figure 1 This is a flowchart illustrating an embodiment of the application service management method of this application;

[0048] Figure 2 This is a schematic diagram of load balancing in Embodiment 1 of the application service management method of this application;

[0049] Figure 3 This is a flowchart illustrating Embodiment 2 of the application service management method of this application;

[0050] Figure 4 This is a schematic diagram of the primary and backup database servers in Embodiment 2 of the application service management method of this application.

[0051] Figure 5 This is a flowchart illustrating Embodiment 3 of the application service management method of this application;

[0052] Figure 6 This is a schematic diagram of the hardware structure involved in the application service management device embodiment of this application. Detailed Implementation

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

[0054] Example 1

[0055] Embodiment 1 of this application discloses an application service management method, which is referred to... Figure 1 The application service management method includes:

[0056] Step S110: When the integration interface receives the application service access instruction, the adaptation interface is determined according to the platform architecture of the application service to be accessed.

[0057] In this embodiment, rules are provided for various software integrated on the same platform, and integration interfaces are also provided for integrating other application software systems. These integration interfaces are used to access application services that require adaptation. The adaptation interface is a lower-level interface below the integration interface, specifically designed for the corresponding platform architecture, and is used to perform specific access actions. The platform architecture refers to the architecture of the software corresponding to the application service, including but not limited to the structural composition of external system interfaces, user interfaces, business logic components, and databases.

[0058] As an optional implementation, when the integration interface receives an access instruction from an application service, it selects the corresponding adaptation interface based on the platform architecture of the application service to be accessed corresponding to the access instruction.

[0059] Step S120: Configure the protocol stack corresponding to the application service to be accessed according to the adaptation interface.

[0060] In this embodiment, the adapter interface supports the configurability of the protocol stack, supporting the Java protocol stack, which is the foundation of basic message broadcasting; it also supports the configuration of additional protocol stacks. Message transmission involves the exchange, encapsulation, inspection, discarding, and retransmission between these protocol stacks. By configuring the upper-layer protocols, message retransmission, large packet decomposition, message packet order, and status detection of machines within the group can be guaranteed.

[0061] As an optional implementation, the protocol stack configuration information corresponding to the access command is obtained, and the protocol stack of the application service to be accessed is configured according to the protocol stack configuration information through the adaptation interface.

[0062] Step S130: Based on the access instruction, determine the required API of the application service to be accessed, and determine the target server corresponding to the application service to be accessed based on the required API.

[0063] In this embodiment, the application service to be accessed may have multiple business capabilities, i.e., multiple required APIs, and the same type of server provides one business support.

[0064] As an optional implementation, the required API corresponding to the application service to be accessed is determined according to the access instruction, the servers in the server cluster are determined according to the type of the required API, and these servers are configured through a symmetric load balancing strategy to be identified as target servers.

[0065] Optionally, step S130 includes:

[0066] Step S131: Determine the service type of the application service to be accessed and the required API based on the access instruction.

[0067] Step S132: Determine the target server based on the business type and the required API.

[0068] As an optional implementation, based on the access information corresponding to the application service to be accessed attached to the access command, the business type and required API that the application service needs to support are determined. Target servers are then determined in the idle server cluster according to the business type and required API, so that the application service to be accessed can be provided through these target servers.

[0069] Step S133: Based on a preset load balancing strategy, the target server is divided into a primary server and a backup server according to a symmetrical structure.

[0070] As an optional implementation, according to a preset load balancing strategy, target servers belonging to the same business service and API requirements are divided into primary servers and backup servers in a symmetrical structure. Each primary and backup server forms a server group, and the primary and backup servers in each server group can provide business support for the application service independently.

[0071] Step S134: Associate and store the server identifiers of the symmetrical master server and the backup server.

[0072] As an optional implementation, the server identifiers of the primary server and backup server in each server group are associated with the business group identifier of the server group and stored together, so that the server in the server group can be quickly located when processing a request.

[0073] Step S140: Generate a configuration file for the application service to be accessed based on the target server and the protocol stack;

[0074] In this embodiment, application configuration information, such as database connection and third-party service keys, is stored in a configuration file instead of being hard-coded directly in the code. This way, when the configuration information needs to be modified, only the configuration file needs to be changed, without needing to recompile and deploy the application.

[0075] As an optional implementation method, based on a preset format, the server information of the target server, the configured protocol stack, and the database connection method, etc., are encapsulated into a configuration file.

[0076] Optionally, step S140 includes:

[0077] Step S141: Determine the business data model based on the data structure of the application service to be accessed.

[0078] Step S142: Determine the data management rules for the application service to be accessed based on the business data model.

[0079] Step S143: Generate the configuration file according to the data management rules, the server identifier, and the protocol stack.

[0080] As an optional implementation, the data structure of the application service to be accessed is obtained according to the access instruction, and the business data model corresponding to the application service to be accessed is determined according to the data structure; the database identifier of the application service to be accessed and the cache identifier of the database corresponding to the database identifier are determined, and the database configuration is determined according to the database identifier and the cache identifier; data management rules are determined according to the business data model and the database configuration, and the configuration file is generated based on the data management rules, the server identifier and the protocol stack.

[0081] Step S150: Execute the access action of the application service to be accessed based on the configuration file and the adaptation interface.

[0082] As an optional implementation, the configuration information of the application service to be connected is determined through a configuration file, and the configuration information is executed through an adaptation interface to complete the connection action.

[0083] The technical solutions described in the embodiments of this application have at least the following technical effects or advantages:

[0084] By employing a process that, upon receiving an application service access command at the integration interface, determines the appropriate interface based on the platform architecture of the application service to be accessed; configures the protocol stack corresponding to the application service based on the appropriate interface; determines the required API of the application service to be accessed based on the access information of the application service to be accessed, and determines the target server corresponding to the application service to be accessed based on the required API; generates a configuration file for the application service to be accessed based on the target server and the protocol stack; and executes the access action of the application service to be accessed based on the configuration file and the appropriate interface, this approach effectively solves the technical problem in related technologies where differences in the construction time, platform architecture, technical routes, and data standards of business systems in different regions make it difficult to achieve information interconnection and interoperability across regions and departments. This, in turn, achieves the technical effect of connecting system platforms with different architectures and improving data governance.

[0085] Based on Embodiment 1, Embodiment 2 of this application proposes an application service management method. Referring to Figure 3, after step S150, the method further includes:

[0086] Step S210: Obtain the target configuration file based on the received pending request and determine the target server group.

[0087] In this embodiment, the pending response request is generated when front-end business personnel perform operations on the corresponding business system while handling business matters. Based on these operations, a corresponding pending response request is generated and sent to the corresponding server in the application service management system to respond to the pending response request.

[0088] As an optional implementation, when a request to be responded to is received, the business system from which the request to be responded to is determined, as well as the application service to which it is directed, the configuration file corresponding to the application service is obtained as the target configuration file, and the target server group to respond to the request is determined based on the configuration data recorded in the target configuration file.

[0089] Step S220: Obtain the load status of the target server group, and determine the target server based on the load status and the load index of the request to be responded to.

[0090] In this embodiment, as Figure 2As shown, load balancing consists of multiple servers arranged symmetrically in a server cluster. Each server has equal status and can independently provide services without the assistance of other servers. Through load balancing technology, incoming requests are evenly distributed to one of the servers in the symmetrical structure, and the server receiving the request responds independently to the client's request. Load balancing can evenly distribute client requests across the server array, thereby providing the ability to quickly retrieve important data and resolve high-concurrency access issues. One server acts as the master server, while the other acts as a backup server. When the master server fails, the backup server takes over as the master server to continue operating and ensure uninterrupted service.

[0091] As an optional implementation, the load status of the target server group is obtained from a monitoring system or load balancer, including the current load and availability information of each server; the load metrics of the requests to be responded to are obtained: based on business needs and performance requirements, the load metrics of the requests to be responded to are determined, such as request processing time, concurrent connections, CPU utilization, etc.; each server in the target server group is traversed, and the degree of difference between the load metrics of each server and the load metrics of the requests to be responded to is calculated; based on the degree of difference, the servers are sorted, and the server whose load metrics best match the requests to be responded to is ranked first; the server with the lowest load is selected as the target server. Factors such as current load, availability, and bandwidth can be considered; the requests to be responded to are forwarded to the target server: the requests to be responded to are redirected or proxied to the selected target server to ensure the efficiency of load balancing and request processing; the load status and performance metrics of the target server are continuously monitored, and if the load is found to be too high or the performance is degraded, load balancing is re-performed, a new target server is selected, and the requests are forwarded.

[0092] Step S230: Determine the transport protocol based on the target configuration file, and forward the request to be responded to to the target server based on the transport protocol.

[0093] Step S240: Control the target server to respond to the request to be responded to.

[0094] As an optional implementation, the transport protocol in the protocol stack is determined based on the configuration data in the target configuration file. Based on the transport protocol, the request to be responded to is forwarded to the corresponding target server, and the target server is controlled to respond to the request to be responded to and forward the business data returned by the target server to the front-end business system.

[0095] Optionally, step S240 includes:

[0096] Step S241: Obtain the data modification details corresponding to the request to be responded to, and record the data modification details to the write-ahead log;

[0097] In this embodiment, when the server responds to a pending request, it writes the content corresponding to the data operation to the write-ahead log before performing data operations on the database.

[0098] As an optional implementation, the details of the data changes corresponding to the request to be responded to are determined, including the specific operations performed on the database. These data change details are then written to a write-ahead log.

[0099] Step S242: Update the main database based on the data modification operations corresponding to the write-ahead log;

[0100] Step S243: Transmit the write-ahead log to the backup database, and replay the data modification operation on the backup database based on the time node.

[0101] As an optional implementation method, refer to Figure 4 The system retrieves data change details recorded in the write-ahead log, determines the corresponding data change operations based on the record's time sequence, and executes these operations in order. It also synchronizes the write-ahead log to the standby database, performing data change operations on the standby database based on the record's time node to ensure data consistency between the primary and standby databases.

[0102] For example, when the primary database server receives each transaction request, it records the data changes in the write-ahead log. Transactions use a two-phase commit approach: first, the changes are written to the write-ahead log, and then the actual database modifications are made. This ensures that the timestamps in the write-ahead log never lag behind the database. Even if the server crashes while writing data, it can recover the data after restarting based on the write-ahead log, because the write-ahead log retains a more recent version than the database records. The write-ahead log is transmitted from the primary database server to the standby database server, and then the changes recorded in the write-ahead log are replayed on the standby database server, thus achieving master-slave replication. Two methods are used to transmit the write-ahead log: archived and streaming.

[0103] In archive-based replication, the primary database server actively copies the write-ahead logs to a safe location, while the standby database server periodically scans this location, copies the write-ahead logs to the standby database server, and then replays them. This ensures that even if the primary database server crashes, the standby database server can obtain a complete record from this safe location, guaranteeing no data loss. Streaming replication simplifies this process, with the primary database server directly transmitting logs to the standby database server via TCP, avoiding the overhead of two replications and reducing data latency between the primary and standby database servers. However, if the primary database server crashes, logs not transmitted to the standby database server will be lost, resulting in data loss. This embodiment supports a hybrid of archive-based and streaming modes. When both modes are enabled, the standby database server periodically checks if archives have reached the designated location and replays the logs. Once no new logs are detected at the designated location, it switches to streaming mode to attempt to transmit logs directly from the network, then checks the archives again, repeating this cycle continuously.

[0104] In this embodiment, when in a high-concurrency, high-performance scenario, using caching space can reduce the load on the backend system, bear most of the read pressure, and greatly improve the system throughput by adding caching before database storage. Meanwhile, in scenarios involving high-speed write operations, some data in the platform needs to be written to the database, and this data is sharded and partitioned, but the reliability of the data is not very high. To reduce the write pressure on the database, this embodiment adopts a batch write operation approach to handle write operations.

[0105] As an optional implementation, the platform shared caching system can achieve linear performance scaling, low latency for transactions and read / write operations; consistent database operations through globally distributed applications; high availability and scalability; convenient distributed node management; dynamic replication and partitioning technologies; persistence with fast parallel recovery; fast in-memory storage, optimized heap memory, data compression, disk overflow reclamation, and data timeout mechanisms; distributed location awareness; support for SQL-like algorithms and indexes; servers can notify clients of data events, responding synchronously or asynchronously to clients while ensuring event order; highly scalable and robust clustering technology; failure detection; and network partition detection.

[0106] This technology effectively solves the technical problem in related technologies where, in high-speed write operations, some data needs to be written to a database, and the data is sharded and partitioned, leading to high request response pressure. It employs a method that involves obtaining a target configuration file based on received requests, determining the target server group, acquiring the load status of the target server group, and determining the target server based on the load status and the load indicators of the requests; determining the transmission protocol based on the target configuration file, and forwarding the requests to the target server based on the transmission protocol; and controlling the target server to respond to the requests.

[0107] Based on Embodiment 1, Embodiment 3 of this application proposes an application service management method, which, after step S150, further includes:

[0108] Step S310: Upon receiving an application service modification request, determine the configuration file to be modified corresponding to the modification request;

[0109] As an optional implementation, when a modification request for an application service is received, the request may contain information such as the items to be modified and the values ​​to be modified. Based on the identifier or other relevant information provided in the request, the configuration files that need to be modified are determined. These can be one or more files.

[0110] Step S320: parse the modification request to determine the item to be modified and the corresponding modification value;

[0111] As an optional implementation, the received modification request is parsed to extract the item to be modified and its corresponding modification value. For example, parsing tools or custom parsing logic can be used to extract the relevant information.

[0112] Step S330: Based on the modified value, perform modification actions on the item to be modified in the configuration file to be modified.

[0113] As an optional implementation, the configuration file to be modified is modified accordingly to ensure that the value of the item to be modified is consistent with the required modification value. Open the configuration file to be modified and locate the corresponding item to be modified. Update or replace the value of the item to be modified according to the modification value provided in the request. Save the modified configuration file to ensure the modification operation takes effect.

[0114] Optionally, after the modification is completed, the application service can be notified of the result. A notification can be sent to the application service informing it of the configuration modification status.

[0115] Optional, refer to Figure 5After step S150, the following steps are also included:

[0116] Step S340: Upon receiving an application service deletion request, determine the configuration file to be deleted corresponding to the deletion request;

[0117] Step S350: Determine the server identifier and data field identifier contained in the configuration file to be deleted;

[0118] Step S360: Release the server corresponding to the server identifier from its occupancy and update the reference relationship of the data field corresponding to the data field identifier;

[0119] Step S370: Delete the configuration file to be deleted.

[0120] As an optional implementation, a deletion request is received, which may contain information about the configuration file to be deleted. Based on the identifier or other relevant information provided in the request, the configuration file to be deleted is determined. The configuration file to be deleted is parsed to determine the server identifier and data field identifier contained therein. Based on the server identifier in the configuration file to be deleted, the corresponding server is released from its occupied state. This can be done by calling the management system or related interfaces to send commands or requests, releasing the server identifier from its occupied state and making it available; updating the server occupancy status in the management system or related systems ensures that other systems are aware of the server's availability. Based on the data field identifier in the configuration file to be deleted, the reference relationships of the relevant data are updated. This can be done by querying the relevant database or data storage system to find the corresponding data items. The data reference relationships are updated, and related fields or relationships are updated or deleted to ensure that the data reference relationships are consistent with the deletion operation of the configuration file. The deletion operation is performed on the configuration file to be deleted; the configuration file to be deleted is opened, and the content and location of the file to be deleted are confirmed; the deletion operation is executed, removing the configuration file to be deleted from the file system. Simultaneously, a backup operation is performed so that the relevant configuration information can be restored or traced in the future.

[0121] In this embodiment, based on the received application service deletion request, the configuration file to be deleted can be determined, along with its server identifier and data field identifier. Then, the server's access can be released, data reference relationships updated, and the deletion action performed. This allows for the deletion of the configuration file while maintaining consistency between the relevant servers and data. This process can be automated, improving efficiency and reducing human error.

[0122] Optionally, step S360 includes:

[0123] Step S361: Update the usage status of the server to idle status;

[0124] Step S362: Determine the single reference field and the ordinary field in the data fields;

[0125] Step S363: Delete the single reference field and delete the reference relationship between the ordinary field and the data field identifier.

[0126] As an optional implementation, based on the server identifier contained in the configuration file to be deleted, the usage status of the corresponding server is updated to idle; the configuration file to be deleted is parsed to determine its data fields, distinguishing between single-reference fields and ordinary fields; for single-reference fields, the associated data item is found based on the data field identifier in the configuration file to be deleted. The single-reference field in the data item is deleted, and the reference relationship is removed from the data item to ensure that it no longer references the field to be deleted; the data item's save is updated to make the deletion operation effective. For ordinary fields, all data items referencing the field are found based on the data field identifier in the configuration file to be deleted; the reference relationship of the corresponding field is deleted in each data item to ensure that it no longer references the field to be deleted; the data item's save is updated to make the deletion of the reference relationship effective.

[0127] Based on the configuration file to be deleted in the deletion request, the server's usage status is updated to idle, and references to single-reference fields and regular fields are removed. This ensures the server status is updated and data references are deleted, guaranteeing the correct deletion of the configuration file and maintaining server and data consistency. This process can be automated, improving efficiency and reducing human error.

[0128] By employing a method that, upon receiving an application service deletion request, determines the configuration file to be deleted corresponding to the request; identifies the server identifier and data field identifier contained in the configuration file; releases the server corresponding to the server identifier from its occupancy and updates the reference relationships of the data fields corresponding to the data field identifier; and then performs the deletion action on the configuration file to be deleted, this approach effectively solves the technical problem of untimely response when application system business capabilities change in related technologies. This enables rapid response to changes in business capabilities, eliminating the need for coding changes when user needs change, and truly achieving on-demand adaptability of the application system without affecting the technical aspects.

[0129] This application also proposes an application service management device, referring to... Figure 6 , Figure 6 This is a schematic diagram of the application service management device structure of the hardware operating environment involved in the embodiments of this application.

[0130] like Figure 6As shown, the application service management device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and 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. The memory 1005 may be a high-speed random access memory or a stable non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0131] Those skilled in the art will understand that Figure 6 The structure shown does not constitute a limitation on the application service management device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0132] Optionally, the memory 1005 is electrically connected to the processor 1001. The processor 1001 can be used to control the operation of the memory 1005 and can also read data in the memory 1005 to implement application service management methods.

[0133] Optionally, such as Figure 6 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a data storage module, a network communication module, a user interface module, and an application service management program.

[0134] Optionally, in Figure 6 In the application service management device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with users; the processor 1001 and memory 1005 in the application service management device of this application can be set in the application service management device.

[0135] like Figure 6 As shown, the application service management device calls the application service management program stored in the memory 1005 through the processor 1001 and executes the relevant steps of the application service management method provided in this application embodiment.

[0136] Furthermore, embodiments of this application also propose a computer-readable storage medium storing an application service management program, which, when executed by a processor, implements the relevant steps of any embodiment of the application service management method described above.

[0137] 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.

[0138] 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.

[0139] 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.

[0140] 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 The steps of the function specified in one or more boxes.

[0141] 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.

[0142] 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.

[0143] 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. An application service management method, characterized in that, The application service management method includes: When the integration interface receives an application service access instruction, it determines the appropriate interface based on the platform architecture of the application service to be accessed. Configure the protocol stack corresponding to the application service to be accessed according to the adaptation interface; Based on the access instruction, determine the required API of the application service to be accessed, and determine the target server corresponding to the application service to be accessed based on the required API. Generate a configuration file for the application service to be accessed based on the target server and the protocol stack; The access action of the application service to be accessed is performed based on the configuration file and the adaptation interface.

2. The application service management method as described in claim 1, characterized in that, The steps of determining the required API of the application service to be accessed based on the access instruction, and determining the target server corresponding to the application service to be accessed based on the required API, include: The service type of the application service to be accessed and the required API are determined based on the access instruction. The target server is determined based on the business type and the required API. Based on a preset load balancing strategy, the target servers are divided into primary servers and backup servers according to a symmetrical structure. The server identifiers of the symmetrical master server and the backup server are associated and stored.

3. The application service management method as described in claim 1, characterized in that, The step of generating the configuration file for the application service to be accessed based on the target server and the protocol stack includes: Based on the data structure of the application service to be accessed, determine the business data model; The data management rules for the application services to be accessed are determined based on the business data model. The configuration file is generated based on the data management rules, the server identifier, and the protocol stack.

4. The application service management method as described in claim 1, characterized in that, After the step of performing the access action of the application service to be accessed based on the configuration file and the adaptation interface, the method further includes: Obtain the target configuration file based on the received pending request, and determine the target server group; Obtain the load status of the target server group, and determine the target server based on the load status and the load index of the request to be responded to; The transport protocol is determined based on the target configuration file, and the request to be responded to is forwarded to the target server based on the transport protocol. Control the target server to respond to the pending request.

5. The application service management method as described in claim 4, characterized in that, The step of controlling the target server to respond to the request to be responded to includes: Obtain the data modification details corresponding to the request to be responded to, and record the data modification details to the write-ahead log; Update the main database based on the data modification operations corresponding to the write-ahead log; The write-ahead log is transmitted to the backup database, and the data modification operations are replayed on the backup database based on the time nodes.

6. The application service management method as described in claim 1, characterized in that, After the step of accessing the application service based on the configuration file and the adaptation interface, the method further includes: Upon receiving an application service modification request, determine the configuration file to be modified corresponding to the modification request; Analyze the modification request to determine the item to be modified and the corresponding modification value; Based on the modified value, perform modification actions on the item to be modified in the configuration file to be modified.

7. The application service management method as described in claim 1, characterized in that, After the step of accessing the application service based on the configuration file and the adaptation interface, the method further includes: Upon receiving an application service deletion request, determine the configuration file to be deleted corresponding to the deletion request; Determine the server identifier and data field identifier contained in the configuration file to be deleted; Release the server corresponding to the server identifier from its occupancy, and update the reference relationship of the data field corresponding to the data field identifier; Perform a deletion action on the configuration file to be deleted.

8. The application service management method as described in claim 7, characterized in that, The steps of releasing the server corresponding to the server identifier and updating the reference relationship of the data field corresponding to the data field identifier include: Update the server's usage status to idle; Identify the single-reference fields and regular fields in the data fields; Delete the single reference field and delete the reference relationship between the ordinary field and the data field identifier.

9. An application service management device, characterized in that, The system includes a memory, a processor, and an application service management program stored in the memory and executable on the processor. When the processor executes the application service management program, it implements the steps of the application service management method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an application service management program, which, when executed by a processor, implements the steps of the application service management method as described in any one of claims 1 to 8.

Images