CN115314559B - Network service system, abnormal response method thereof, service unit, scheduling processing unit, electronic device and computer storage medium - Google Patents
Network service system, abnormal response method thereof, service unit, scheduling processing unit, electronic device and computer storage medium Download PDFInfo
- Publication number
- CN115314559B CN115314559B CN202210925835.2A CN202210925835A CN115314559B CN 115314559 B CN115314559 B CN 115314559B CN 202210925835 A CN202210925835 A CN 202210925835A CN 115314559 B CN115314559 B CN 115314559B
- Authority
- CN
- China
- Prior art keywords
- service
- execution
- unit
- service unit
- execution information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application provides a network service system and an abnormal response method thereof.A scheduling processing unit determines service units to be called and a calling sequence among the service units according to service logic; each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier and is used for representing the execution result of each link in the execution process of the service; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme. According to the scheme, the exception handling scheme is automatically executed, the participation of a user is not needed, the operation of a user side is reduced, and the user experience is improved.
Description
Technical Field
The application relates to the technical field of software, in particular to a network service system and an abnormal response method thereof.
Background
In the big data age, service systems have emerged that consist of a large number of micro services that are decoupled from each other. The plurality of service units in the large-scale software are generally scheduled and managed by a background management program in a unified mode, and are packaged into a software package together with a acquired management program and deployed on a service. The micro-services are distinguished from service units in large software by the following: the plurality of micro service units may be distributed on one server entity or may be distributed on a plurality of different server entities; each micro service unit can independently realize one service operation and independently present the operation result to the user; different service units are typically responsible for different service units; each micro-service is a lightweight software program.
Currently, a user executes a plurality of micro services with functional relevance one by one, and after one micro service is executed, the execution result of the micro service is used in the execution process of another micro service. Some users write small programs, and the operations which are needed to be manually executed in the process of executing the micro-services one by one are automatically executed by adopting the programs.
In the existing operation methods, in order to accurately locate the cause of the execution abnormality, the abnormal execution result of each micro service is presented to the user, and the user processes the abnormal execution result. Therefore, the operation of the user is complicated, and the experience is poor.
Disclosure of Invention
The application aims to provide a network service system and an abnormal response method thereof, which are used for solving the problems of complex operation and poor experience of a user in the existing micro-service execution method.
In order to solve the above technical problems, a first aspect of the present disclosure provides an exception response method for a network service system, where a scheduling processing unit and a plurality of service units are set in the network service system, each service unit executes a service, the service units are decoupled from each other, and the scheduling processing unit determines a service unit to be called and a calling sequence between the service units according to service logic; the method comprises the following steps: each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier and is used for representing the execution result of each link in the execution process of the service; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme.
In some embodiments, determining the exception handling scheme according to feedback information of each service unit associated with the user identifier includes: determining whether the execution abnormality is a reason of network transmission according to the execution information fed back by each service unit associated with the user identifier; if yes, determining an exception handling scheme comprises re-invoking the target service unit to execute service; if not, determining an exception handling scheme includes determining a replacement unit for the target service unit and invoking the replacement unit to perform a service.
In some embodiments, determining whether the execution anomaly is a cause of network transmission according to the execution information fed back by each service unit associated with the user identifier includes: and determining whether the execution abnormality is a cause of network transmission according to the content in the execution information fed back by the target service unit.
In some embodiments, determining whether the execution anomaly is a cause of network transmission according to the execution information fed back by each service unit associated with the user identifier includes: determining the execution sequence among the service units associated with the user identifier according to the execution information fed back by the service units associated with the user identifier; and inputting feedback information of each service unit associated with the user identifier and an execution sequence among the service units associated with the user identifier into a predetermined network model, and determining whether the execution abnormality is a cause of network transmission according to an output result of the network model.
In some embodiments, the method further comprises: at least one of the following indexes of each service unit associated with the user identification is counted: the number of execution exceptions, the cause of the execution exception, the execution time; determining whether a network transmission problem exists according to the statistical result; if the network transmission scheme exists, a first notification is sent to the network transmission equipment at the user side, so that the network transmission equipment can be used for optimizing the network transmission scheme; determining whether a user operation problem exists according to the statistical result; if so, sending operation help information to the user side.
In some embodiments, the method further comprises: counting at least one index of each service unit in the plurality of service units: the number of execution exceptions, the cause of the execution exception, the execution time; judging whether each service unit has abnormality according to the statistical result; and sending a second notification to the service provider of the service unit with abnormal judgment result, wherein the second notification is used for optimizing the service unit by the service provider.
A second aspect of the present specification provides a network service system, comprising: a plurality of service units, wherein each service unit executes a service, and the service units are mutually decoupled; each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier and is used for representing the execution result of each link in the execution process of the service; the scheduling processing unit is used for determining the service units to be called and the calling sequence among the service units according to the service logic; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme.
A third aspect of the present specification provides a service unit, including: each service unit executes a service, and the service units are mutually decoupled; the method comprises the steps that in the process of calling and executing one service, each service unit feeds back execution information to a dispatching processing unit, the execution information carries user identification, and the execution information is used for representing execution results of each link in the service execution process and is used for determining the service units needing to be called and calling sequences among the service units according to service logic by the dispatching processing unit; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme.
A fourth aspect of the present specification provides a scheduling processing unit configured to perform: determining service units to be called and a calling sequence among the service units according to service logic; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; automatically executing the exception handling scheme; wherein, each service unit executes a service, and the service units are mutually decoupled; and each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier, and the execution information is used for representing the execution result of each link in the execution process of the service.
A fifth aspect of the present specification provides an electronic device, comprising: the system comprises a memory and a processor, wherein the processor and the memory are in communication connection, the memory stores computer instructions, and the processor realizes the steps of the method in any one of the first aspect by executing the computer instructions.
A sixth aspect of the present description provides a computer storage medium storing computer program instructions which, when executed by a processor, implement the steps of the method of any one of the first aspects.
According to the network service system and the abnormal response method thereof provided by the specification, a plurality of service units which are decoupled from each other and can realize one service are scheduled through the scheduling processing unit so as to realize one operation flow of a user; in the process of calling and executing one service, each service unit feeds back the execution result of each link and also feeds back the user identification, and under the condition that the service units execute abnormally, an abnormal processing scheme is determined according to the execution information fed back by each service unit associated with the service identification, and the abnormal processing scheme is automatically executed, so that the participation of a user is not needed, the operation of a user side is reduced, and the user experience is improved. The proposal can integrate various light-weight existing micro services together to form a large service system, fully exert the specialty of each micro service provider and reduce the development cost of the system when providing integrated high-quality services for users; the method can accurately locate the abnormal position and process the abnormal condition, and improves the reliability of the integrated system.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are necessary for the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the following description are only some of the embodiments described in the application, and that other drawings can be obtained from these drawings without inventive effort for a person skilled in the art.
FIG. 1 shows a schematic diagram of a network service system provided herein;
FIG. 2 is a flow chart showing the method of responding to anomalies in a network service system provided in this specification;
fig. 3 shows a functional block diagram of an electronic device provided in the present specification.
Detailed Description
In order to make the technical solution of the present application better understood by those skilled in the art, the technical solution of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments of the present application. All other embodiments, based on the embodiments of the application, which would be apparent to one of ordinary skill in the art without undue burden are intended to be within the scope of the application.
The specification provides an abnormal response method of a network service system, which is used for a large-scale network service system composed of a large number of mutually decoupled micro services, simplifies the operation of a user when the network service system is abnormal, and improves the experience of the user.
The abnormal response method of the network service system provided in the present specification may be used for the network service system shown in fig. 1, which includes a scheduling processing unit and a plurality of service units. Each service unit executes a service, the services are decoupled mutually, and a scheduling processing unit determines the service units needing to be called and the calling sequence among the service units according to service logic.
That is, there is no relationship of call-to-call between any two service units among the plurality of service units. And after the execution is finished, the service unit sends the execution result to the scheduling processing unit for scheduling processing. The data required by one service unit when executing is not directly sourced from another service unit, but rather from the dispatch processing unit.
The service unit in this specification may refer to a micro-service program in the background art.
As shown in fig. 2, the abnormal response method of the network service system provided in the present specification includes the following steps:
s10: and each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier and is used for representing the execution result of each link in the execution process of the service.
When the user uses the network service system to perform target operation, the service system can allocate a user identifier to the user as a unique identity identifier of the user. The target operation may be formed by execution results of a plurality of service units, where each service unit feeds back execution information to the scheduling processing unit, where the execution information carries a user identifier, and the execution information is used to represent execution results of links in the execution process of the service.
For each service, the execution result is composed of a plurality of links, and these links may be, for example, receiving data, processing data, storing data, connecting databases, requesting data from a server, responding to page content, and the like.
In some embodiments, the feedback execution information may be a service-related execution result or a network-related execution result. The service unit writes the execution result of the service aspect in a log file in the process of executing the service and sends the log file to the scheduling processing unit; the results of the execution of the network aspects are typically in response data specified by the network protocol, e.g. in the HTTP network protocol, the results of the HTTP network transmission or request are indicated by a return status code, in HTTP1.1, 100-199 is used to specify certain actions that the client should respond to, 200-299 is used to indicate that the request was successful, 300-399 is used for files that have moved and is often contained in the location header information to specify new address information, 400-499 is used to indicate errors for the client, 500-599 is used to support server errors. The execution result of the network aspect can be set in the HTTP return status codes, TCP and UDP return status codes.
The method provided in the present specification requires that the method corresponds to the user identifier, whether it is the result of the execution of the service or the result of the execution of the network. For example, after a return status code is acquired, the user identification corresponding thereto should be determined.
S20: and determining whether each service unit is abnormal according to the execution information fed back by each service unit.
For the execution information written in the log, it is generally possible to determine that the execution is normal by "Success", "OK", "Success", and the like, and to determine that the execution is abnormal by words such as "Fail", and the like. Of course, whether normal execution is performed may be determined according to the agreed code.
S30: and under the condition that the target service unit is abnormal in execution, acquiring the user identification from the execution information fed back by the target service unit which is abnormal in execution.
Because each piece of execution information fed back carries the user identification, under the condition that the execution of the target service unit is abnormal, the user identification can be determined from the fed back execution information, so that the user can know which operation performed by the user is abnormal.
S40: and determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier.
In some embodiments, step S40 may include the steps of:
s41: and determining whether the execution abnormality is the reason of network transmission according to the execution information fed back by each service unit associated with the user identifier.
In some embodiments, whether the network transmission cause is determined according to the content of the execution information fed back by the target service unit, and in some embodiments, whether the network transmission cause is determined according to network transmission indexes such as processing delay, network jitter, packet loss rate, bandwidth, rate, heartbeat and the like, for example, if one of the network transmission indexes is obvious, the abnormality is likely to be the execution abnormality caused by the transmission cause.
In some embodiments, S41 may determine whether the execution exception is the cause of the network transmission by: determining the execution sequence among the service units associated with the user identifier according to the execution information fed back by the service units associated with the user identifier; and inputting feedback information of each service unit associated with the user identifier and an execution sequence among the service units associated with the user identifier into a predetermined first network model, and determining whether the execution abnormality is a cause of network transmission according to an output result of the first network model. Here, the output result of the first network model may be "whether or not it is an execution abnormality caused by the network transmission cause", or may be other contents, and whether or not it is an execution abnormality caused by the network transmission cause is further determined based on the output result of the first network model.
The first network model may be trained by: acquiring abnormal service in the history execution process of the method shown in fig. 1, acquiring user identification in execution information fed back by a service unit of the abnormal service, feeding back the execution information fed back by each service unit associated with the user identification, and determining the execution sequence among the service units associated with the user identification; and taking feedback information of each service unit associated with the user identifier, the execution sequence and abnormal execution result among the service units associated with the user identifier as a training sample. According to the method, a large number of training samples are obtained, feedback information of each service unit associated with the user identifier and execution sequence among the service units associated with the user identifier are used as input of a first network model, abnormal execution results are used as output of the network model, and the first network model is trained. The exception execution result may be defined as needed.
S42: if yes, determining that the exception handling includes re-invoking the target service unit to perform the service.
In the case of unstable network transmission quality, the target service unit may execute the service again successfully.
S43: if not, determining that the exception handling scheme comprises a replacement unit of the target service unit and calling the replacement unit to execute the service.
The replacement unit may be one service unit or a plurality of service units executed in sequence. Among the plurality of service units sequentially executed, a service unit that compensates for a result that has been caused by an abnormal service unit may be included. For example, the exception service unit successfully modifies the data in the database, and the replacement unit may include a service unit that changes the modified data of the exception service unit back to the original data.
In some embodiments, S43 may determine the association between each target service unit and the replacement unit in advance, so that after determining the target service unit that performs abnormality, the replacement unit may be determined according to the association.
In some embodiments, S43 may determine the replacement unit by: determining the execution sequence among the service units associated with the user identifier according to the execution information fed back by the service units associated with the user identifier; and inputting feedback information of each service unit associated with the user identifier and the execution sequence among the service units associated with the user identifier into a second predetermined network model to obtain the substitution unit.
The second network model may be trained by: acquiring abnormal service in the history execution process of the method shown in fig. 1, acquiring user identification in execution information fed back by a service unit of the abnormal service, feeding back the execution information fed back by each service unit associated with the user identification, and determining the execution sequence among the service units associated with the user identification; acquiring the sequence among the service units which are successful in processing the abnormal service; and taking feedback information of each service unit associated with the user identifier and the execution sequence among the service units associated with the user identifier as input of a second network model, and taking the sequence among the service units successfully processed by abnormal service and each service unit as output of the network model to train the second network model.
S50: and automatically executing the exception handling scheme.
According to the network service system abnormal response method provided by the specification, the plurality of service units which are decoupled from each other and can realize one service are scheduled through the scheduling processing unit, so that one operation flow of a user is realized; in the process of calling and executing one service, each service unit feeds back the execution result of each link and also feeds back the user identification, and under the condition that the service units execute abnormally, an abnormal processing scheme is determined according to the execution information fed back by each service unit associated with the service identification, and the abnormal processing scheme is automatically executed, so that the participation of a user is not needed, the operation of a user side is reduced, and the user experience is improved. The proposal can integrate various light-weight existing micro services together to form a large service system, fully exert the specialty of each micro service provider and reduce the development cost of the system when providing integrated high-quality services for users; the method can accurately locate the abnormal position and process the abnormal condition, and improves the reliability of the integrated system.
In some embodiments, the network service system exception response method provided in the present specification further includes: at least one of the following indexes of each service unit associated with the user identification is counted: the number of execution exceptions, the cause of the execution exception, the execution time; determining whether a network transmission problem exists according to the statistical result; if the network transmission scheme exists, a first notification is sent to the network transmission equipment at the user side, so that the network transmission equipment can be used for optimizing the network transmission scheme; determining whether a user operation problem exists according to the statistical result; if yes, sending operation help information to the user side so as to guide the operation of the user.
In some embodiments, the network service system exception response method provided in the present specification further includes: counting at least one index of each service unit in the plurality of service units: the number of execution exceptions, the cause of the execution exception, the execution time; judging whether each service unit has abnormality according to the statistical result; and sending a second notification to the service provider of the service unit with abnormal judgment result, wherein the second notification is used for optimizing the service unit by the service provider.
The present disclosure also provides a network service system, as shown in fig. 1, including a scheduling unit and a plurality of service units.
Wherein, each service unit executes a service, and the service units are mutually decoupled; each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier and is used for representing the execution result of each link in the execution process of the service;
the scheduling processing unit is used for determining the service units to be called and the calling sequence among the service units according to the service logic; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme.
The present disclosure also provides a service unit, which may be the service unit in fig. 1. Each service unit executes a service, and the service units are mutually decoupled; the method comprises the steps that in the process of calling and executing one service, each service unit feeds back execution information to a dispatching processing unit, the execution information carries user identification, and the execution information is used for representing execution results of each link in the service execution process and is used for determining the service units needing to be called and calling sequences among the service units according to service logic by the dispatching processing unit; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme.
The present specification also provides a scheduling processing unit, which may be the scheduling processing unit in fig. 2. The scheduling processing unit is used for executing the following operations: determining service units to be called and a calling sequence among the service units according to service logic; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; automatically executing the exception handling scheme; wherein, each service unit executes a service, and the service units are mutually decoupled; and each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier, and the execution information is used for representing the execution result of each link in the execution process of the service.
The description and beneficial effects of the network service system, the scheduling processing unit and the service unit can refer to the description and beneficial effects of the method part, and are not repeated.
The present application also provides an electronic device, as shown in fig. 3, which may include a processor 301 and a memory 302, where the processor 301 and the memory 302 may be connected by a bus or other means, and in fig. 3, the connection is exemplified by a bus.
The processor 301 may be a central processing unit (Central Processing Unit, CPU). The processor 301 may also be a chip such as other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination thereof.
The memory 302 serves as a non-transitory computer readable storage medium that may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules that schedule processing units or service units in embodiments of the application. The processor 301 executes various functional applications of the processor and data classification by running non-transitory software programs, instructions, and modules stored in the memory 302, that is, implements the web service system anomaly response method in the above-described method embodiment.
Memory 302 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created by the processor 301, etc. In addition, memory 302 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 302 may optionally include memory located remotely from processor 301, such remote memory being connectable to processor 301 through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The one or more modules are stored in the memory 302, which when executed by the processor 301, perform the web service system exception response method of the embodiment shown in fig. 2.
The details of the above electronic device may be understood by referring to the related descriptions and effects in the corresponding embodiment of fig. 2, which are not repeated here.
The present description provides a computer storage medium having stored thereon computer program instructions which when executed by a processor perform the steps of the method shown in fig. 2.
It will be appreciated by those skilled in the art that implementing all or part of the above-described embodiment method may be implemented by a computer program to instruct related hardware, where the program may be stored in a computer readable storage medium, and the program may include the above-described embodiment method when executed. Wherein the storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a Flash Memory (Flash Memory), a Hard Disk (HDD), or a Solid State Drive (SSD); the storage medium may also comprise a combination of memories of the kind described above.
In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips 2. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented with "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but HDL is not only one, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog2 are most commonly used at present. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are referred to each other, and each embodiment is mainly described as different from other embodiments.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.
From the above description of embodiments, it will be apparent to those skilled in the art that the present application may be implemented in software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method of some parts of the various embodiments of the present application.
The application is operational with numerous general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
While the present application has been described by way of embodiments, those of ordinary skill in the art will recognize that there are many variations and modifications of the present application without departing from the spirit of the application, and it is intended that the appended claims encompass such variations and modifications as do not depart from the spirit of the application.
Claims (10)
1. A network service system exception response method is characterized in that a dispatching processing unit and a plurality of service units are arranged in a network service system, each service unit executes a service, the service units are mutually decoupled, and the dispatching processing unit determines the service units needing to be called and the calling sequence among the service units according to service logic; the method comprises the following steps:
each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier and is used for representing the execution result of each link in the execution process of the service;
determining whether each service unit is abnormal according to the execution information fed back by each service unit;
under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution;
determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier;
and automatically executing the exception handling scheme.
2. The method of claim 1, wherein determining the exception handling scheme based on feedback information for each service unit associated with the user identification comprises:
determining whether the execution abnormality is a reason of network transmission according to the execution information fed back by each service unit associated with the user identifier;
if yes, determining an exception handling scheme comprises re-invoking the target service unit to execute service;
if not, determining an exception handling scheme includes determining a replacement unit for the target service unit and invoking the replacement unit to perform a service.
3. The method of claim 1, wherein determining whether the execution anomaly is a cause of network transmission based on the execution information fed back by each service element associated with the user identifier, comprises:
and determining whether the execution abnormality is a cause of network transmission according to the content in the execution information fed back by the target service unit.
4. The method of claim 1, wherein determining whether the execution anomaly is a cause of network transmission based on the execution information fed back by each service element associated with the user identifier, comprises:
determining the execution sequence among the service units associated with the user identifier according to the execution information fed back by the service units associated with the user identifier;
and inputting feedback information of each service unit associated with the user identifier and an execution sequence among the service units associated with the user identifier into a predetermined network model, and determining whether the execution abnormality is a cause of network transmission according to an output result of the network model.
5. The method as recited in claim 1, further comprising:
at least one of the following indexes of each service unit associated with the user identification is counted: the number of execution exceptions, the cause of the execution exception, the execution time;
determining whether a network transmission problem exists according to the statistical result;
if the network transmission scheme exists, a first notification is sent to the network transmission equipment at the user side, so that the network transmission equipment can be used for optimizing the network transmission scheme;
determining whether a user operation problem exists according to the statistical result;
if so, sending operation help information to the user side.
6. A network service system, comprising:
a plurality of service units, wherein each service unit executes a service, and the service units are mutually decoupled; each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier and is used for representing the execution result of each link in the execution process of the service;
the scheduling processing unit is used for determining the service units to be called and the calling sequence among the service units according to the service logic; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme.
7. A service unit, comprising: each service unit executes a service, and the service units are mutually decoupled; the method comprises the steps that in the process of calling and executing one service, each service unit feeds back execution information to a dispatching processing unit, the execution information carries user identification, and the execution information is used for representing execution results of each link in the service execution process and is used for determining the service units needing to be called and calling sequences among the service units according to service logic by the dispatching processing unit; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; and automatically executing the exception handling scheme.
8. A dispatch processing unit, configured to perform the operations of:
determining service units to be called and a calling sequence among the service units according to service logic; determining whether each service unit is abnormal according to the execution information fed back by each service unit; under the condition that the target service unit is abnormal in execution, acquiring a user identifier from the execution information fed back by the target service unit which is abnormal in execution; determining an exception handling scheme according to the execution information fed back by each service unit associated with the user identifier; automatically executing the exception handling scheme; wherein, each service unit executes a service, and the service units are mutually decoupled; and each service unit feeds back execution information to the scheduling processing unit in the process of being called to execute one service, wherein the execution information carries a user identifier, and the execution information is used for representing the execution result of each link in the execution process of the service.
9. An electronic device, comprising:
a memory and a processor in communication with each other, the memory having stored therein computer instructions which, upon execution, cause the processor to perform the steps of the method of any of claims 1 to 5.
10. A computer storage medium storing computer program instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210925835.2A CN115314559B (en) | 2022-08-03 | 2022-08-03 | Network service system, abnormal response method thereof, service unit, scheduling processing unit, electronic device and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210925835.2A CN115314559B (en) | 2022-08-03 | 2022-08-03 | Network service system, abnormal response method thereof, service unit, scheduling processing unit, electronic device and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115314559A CN115314559A (en) | 2022-11-08 |
| CN115314559B true CN115314559B (en) | 2023-09-29 |
Family
ID=83858527
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210925835.2A Active CN115314559B (en) | 2022-08-03 | 2022-08-03 | Network service system, abnormal response method thereof, service unit, scheduling processing unit, electronic device and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115314559B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109933452A (en) * | 2019-03-22 | 2019-06-25 | 中国科学院软件研究所 | A kind of micro services intelligent monitoring method towards anomalous propagation |
| CN111240876A (en) * | 2020-01-06 | 2020-06-05 | 远光软件股份有限公司 | Fault positioning method and device for microservice, storage medium and terminal |
| WO2021008031A1 (en) * | 2019-07-16 | 2021-01-21 | 平安普惠企业管理有限公司 | Processing method for implementing monitoring intellectualization on the basis of micro-services, and electronic device |
| CN112667457A (en) * | 2019-10-16 | 2021-04-16 | 烽火通信科技股份有限公司 | Method and system for monitoring service call under micro-service architecture |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10073767B2 (en) * | 2017-01-18 | 2018-09-11 | Pivotal Software, Inc. | Trace Management |
-
2022
- 2022-08-03 CN CN202210925835.2A patent/CN115314559B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109933452A (en) * | 2019-03-22 | 2019-06-25 | 中国科学院软件研究所 | A kind of micro services intelligent monitoring method towards anomalous propagation |
| WO2021008031A1 (en) * | 2019-07-16 | 2021-01-21 | 平安普惠企业管理有限公司 | Processing method for implementing monitoring intellectualization on the basis of micro-services, and electronic device |
| CN112667457A (en) * | 2019-10-16 | 2021-04-16 | 烽火通信科技股份有限公司 | Method and system for monitoring service call under micro-service architecture |
| CN111240876A (en) * | 2020-01-06 | 2020-06-05 | 远光软件股份有限公司 | Fault positioning method and device for microservice, storage medium and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115314559A (en) | 2022-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10528454B1 (en) | Intelligent automation of computer software testing log aggregation, analysis, and error remediation | |
| EP3404542A1 (en) | Data pipeline architecture for analytics processing stack | |
| CN112162915B (en) | Test data generation method, device, equipment and storage medium | |
| CN112507029A (en) | Data processing system and data real-time processing method | |
| CN110297944B (en) | Distributed XML data processing method and system | |
| CN108900627B (en) | Network request method, terminal device and storage medium | |
| CN115114044A (en) | Message pushing method, device, equipment and medium | |
| CN113342503B (en) | Real-time progress feedback method, device, equipment and storage medium | |
| CN115329170A (en) | Webpage crawling method, device, equipment and storage medium | |
| CN114827280A (en) | Request processing method, device, equipment and medium | |
| CN115314559B (en) | Network service system, abnormal response method thereof, service unit, scheduling processing unit, electronic device and computer storage medium | |
| CN112765246B (en) | Task processing method, device, electronic equipment and storage medium | |
| CN112565277B (en) | Data transmission method, system and electronic equipment | |
| CN101562622A (en) | Method for executing user request and corresponding server thereof | |
| CN112637288A (en) | Streaming data distribution method and system | |
| CN114880321A (en) | Service early warning method and device | |
| CN113595795A (en) | Network communication method, device, system, equipment and medium | |
| CN112769741B (en) | Message communication method and electronic equipment | |
| CN113568966A (en) | Data processing method and system used between ODS layer and DW layer | |
| CN113722115A (en) | Method, device, equipment and computer readable medium for calling interface | |
| CN110569673A (en) | Data file processing method, device, equipment and storage medium | |
| CN113760372B (en) | Binary data packet analysis method and system | |
| CN113015203B (en) | Information acquisition method, device, terminal, system and storage medium | |
| US11968280B1 (en) | Controlling ingestion of streaming data to serverless function executions | |
| CN112887390B (en) | Network request method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |