CN113110963A - Service processing method, service processing device, electronic equipment and readable storage medium - Google Patents
Service processing method, service processing device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN113110963A CN113110963A CN202110469525.XA CN202110469525A CN113110963A CN 113110963 A CN113110963 A CN 113110963A CN 202110469525 A CN202110469525 A CN 202110469525A CN 113110963 A CN113110963 A CN 113110963A
- Authority
- CN
- China
- Prior art keywords
- service
- component
- processing
- business
- processed
- 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.)
- Pending
Links
- 238000012545 processing Methods 0.000 title claims abstract description 119
- 238000003672 processing method Methods 0.000 title claims abstract description 23
- 238000000034 method Methods 0.000 claims abstract description 74
- 230000008569 process Effects 0.000 claims abstract description 43
- 238000004590 computer program Methods 0.000 claims abstract description 27
- 230000006870 function Effects 0.000 claims description 16
- 230000015654 memory Effects 0.000 claims description 12
- 230000004044 response Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 21
- 238000004891 communication Methods 0.000 description 7
- 108010001267 Protein Subunits Proteins 0.000 description 5
- 238000012795 verification Methods 0.000 description 5
- 238000012827 research and development Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004806 packaging method and process Methods 0.000 description 3
- 208000017667 Chronic Disease Diseases 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 239000000758 substrate Substances 0.000 description 2
- 230000001502 supplementing effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000012512 characterization method Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000003814 drug Substances 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/28—Error detection; Error correction; Monitoring by checking the correct order of processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the disclosure provides a service processing method, a service processing device, an electronic device, a computer readable storage medium and a computer program product, which can be used in the technical field of computers or other fields. The method comprises the following steps: acquiring a service processing request for processing a service to be processed, wherein the service processing request comprises a service scene identifier of the service to be processed; responding to a service processing request, and determining a plurality of service components for processing the service to be processed according to the service scene identification, wherein each service component is created according to service logic; determining an execution order of a plurality of business components; and calling a plurality of service components according to the execution sequence to process the service to be processed.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a service processing method, a service processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.
Background
In order to meet the increasing business demands, business codes for different business scenarios need to be developed.
In implementing the disclosed concept, the inventors found that there is at least the following technical problem in the related art, in which the code reuse rate is low.
Disclosure of Invention
In view of this, the embodiments of the present disclosure provide a service processing method, a service processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.
One aspect of the embodiments of the present disclosure provides a service processing method, including: acquiring a service processing request for processing a service to be processed, wherein the service processing request comprises a service scene identifier of the service to be processed; responding to the service processing request, and determining a plurality of service components for processing the service to be processed according to the service scene identification, wherein each service component is created according to service logic; determining an execution sequence of the plurality of business components; and calling the plurality of service components according to the execution sequence to process the service to be processed.
According to an embodiment of the present disclosure, each of the service components is created according to a service logic, and includes: creating an assembly parent class, wherein the assembly parent class is a class for representing an interface required to be called for processing the business logic; creating a component template class, wherein the component template class is a class which is characterized by being capable of providing a common function, and the common function is obtained by analyzing the business logic; creating a component implementation class, wherein the component implementation class is a class which represents that the service logic can be executed; and creating the business component according to the component parent class, the component template class and the component implementation class.
According to an embodiment of the present disclosure, the creating a component template class includes: creating a common flow, wherein the common flow is a common flow for representing and processing the business logic; creating a common template, wherein the service template is a common tool required for characterizing and processing the service logic; creating a flow logic, wherein the flow logic is a sequence for representing and processing each flow included in the business logic; and creating the component template class according to the common flow, the common template and the flow logic.
According to an embodiment of the present disclosure, further comprising: storing the plurality of business components in a component list; the invoking the plurality of service components according to the execution sequence to process the service to be processed includes: and calling the service components in the component list according to the execution sequence to process the service to be processed.
According to an embodiment of the present disclosure, the invoking the service components in the component list according to the execution sequence to process the service to be processed includes: calling a first service component from the component list according to the execution sequence; executing the first service component to process the processing service; deleting the first service component from the component list; and under the condition that the execution result of the first service component is determined to be successful, if the component list is determined to be empty, finishing processing the service to be processed.
According to an embodiment of the present disclosure, further comprising: and if the component list is not determined to be empty, calling a second service component from the component list according to the execution sequence until the component list is determined to be empty.
According to an embodiment of the present disclosure, further comprising: and under the condition that the execution result of the first business component is determined to be the execution failure, if the first business component is determined to be executed again, the first business component is executed again.
Another aspect of the embodiments of the present disclosure provides a service processing apparatus, including: the device comprises an acquisition module, a first determination module, a second determination module and a processing module. Wherein: an obtaining module, configured to obtain a service processing request for processing a service to be processed, where the service processing request includes a service scene identifier of the service to be processed; a first determining module, configured to determine, in response to the service processing request, a plurality of service components for processing the service to be processed according to the service scene identifier, where each service component is created according to a service logic; a second determining module, configured to determine an execution order of the plurality of service components; and the processing module is used for calling the plurality of service components according to the execution sequence so as to process the service to be processed.
Another aspect of an embodiment of the present disclosure provides an electronic device including: one or more processors; memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.
Another aspect of embodiments of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program product comprising computer executable instructions for implementing the method as described above when executed.
According to the embodiment of the disclosure, after a service processing request is received, the execution sequence of a plurality of service components and the execution sequence of the plurality of service components for processing the service to be processed are determined according to the service scene identification, and the plurality of service components are called according to the execution sequence to process the service to be processed. Because the mode of separating the service components from the execution sequence is adopted, different service requests can be met by adjusting the execution sequence and the related specific service components, and the service components can be multiplexed, thereby effectively reducing code redundancy and improving code multiplexing rate.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:
fig. 1 schematically shows an exemplary system architecture to which a traffic processing method may be applied according to an embodiment of the present disclosure;
FIG. 2 schematically shows a flow diagram of a traffic handling method according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a schematic diagram of business components included in a business system according to an embodiment of the disclosure;
FIG. 4 schematically illustrates a structural diagram of a business component in accordance with an embodiment of the disclosure;
FIG. 5 schematically shows a schematic diagram of a business process according to an embodiment of the disclosure;
FIG. 6 is a schematic diagram that schematically illustrates logical relationships between business components in a business step, in accordance with an embodiment of the present disclosure;
FIG. 7 schematically shows a business process flow according to another embodiment of the disclosure;
fig. 8 is a diagram schematically illustrating a data structure of a service execution order according to an embodiment of the present disclosure;
fig. 9 schematically shows a block diagram of a traffic processing device according to an embodiment of the present disclosure;
fig. 10 schematically shows a block diagram of an electronic device adapted to implement a traffic processing method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "A, B, at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
In the current business scenario, different nodes for different scenarios have their own unique content. Taking internet medical service as an example, the inquiry process may include: pre-inquiry of a patient, generation of an inquiry bill, payment, reception of a diagnosis, prescription making, completion of the inquiry or cancellation of the inquiry; however, specifically for the physical examination inquiry service, when the inquiry sheet is generated, the number of the physical examination report of the third party needs to be written into the inquiry sheet, so that the doctor can easily interpret the imported physical examination report during the medical examination. For another example, the process of the inquiry including the post-diagnosis management service may further include: automatically binding the relationship of the doctor and the patient and sending the chat right after generating the inquiry list; specifically, for the expert team service, after payment is successful, a group chat containing all the experts of the expert team is created for a patient to perform inquiry; for the chronic disease service, a group chat containing all people in the chronic disease team is created for a patient to perform an inquiry at the time of receiving a visit.
In view of the above unique content, a developer is required to write a large amount of service codes in each node, and since the service codes are many repetitions, redundant codes exist in the nodes.
Based on the above technical problem, the inventor proposes a service processing method, which writes service codes into independent units and implements complex services by controlling the call sequence between the independent units. By the method, the research and development difficulty can be reduced, the reuse degree of the service codes can be improved, the research and development efficiency can be improved, and the redundancy of the service codes can be reduced under the conditions that the service flow is frequently changed and the flow is continuously adjusted.
The method provided by the embodiment of the disclosure is as follows. Embodiments of the present disclosure provide a service processing method, a service processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product. The service processing method comprises the steps of obtaining a service processing request for processing a service to be processed, wherein the service processing request comprises a service scene identifier of the service to be processed; responding to a service processing request, and determining a plurality of service components for processing the service to be processed according to the service scene identification, wherein each service component is created according to service logic; determining an execution order of a plurality of business components; and calling a plurality of service components according to the execution sequence to process the service to be processed.
Fig. 1 schematically shows an exemplary system architecture to which a traffic processing method may be applied according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the system architecture according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. Various client applications may be installed on the terminal devices 101, 102, 103, including but not limited to browser-like applications, communication-like applications, social-like applications, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server that provides various services, and a user may send a business process request to the server 105 using a client application in the terminal device 101, 102, 103. The server 105 may extract corresponding service components 1061 from the service component library 106 according to the service scene identifier corresponding to the service processing request, and arrange the service components 1061 according to the execution sequence preset in the service scene identifier, so as to obtain the component list 107. By the sequential execution of the service components 1061 in the component list 107, the server 105 can complete the service processing request of the user and feed back the processing result to the terminal device.
It should be noted that the service processing method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the service processing device provided by the embodiment of the present disclosure may be generally disposed in the server 105. The service processing method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Correspondingly, the service processing apparatus provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Alternatively, the service processing method provided by the embodiment of the present disclosure may also be executed by the terminal device 101, 102, or 103, or may also be executed by another terminal device different from the terminal device 101, 102, or 103. Correspondingly, the service processing apparatus provided by the embodiment of the present disclosure may also be disposed in the terminal device 101, 102, or 103, or in another terminal device different from the terminal device 101, 102, or 103.
For example, the preset service component library 106 may be originally stored in any one of the terminal devices 101, 102, or 103 (for example, but not limited to, the terminal device 101), or stored on an external storage device and may be imported into the terminal device 101. After receiving a service request submitted by a user, the terminal device 101 may locally execute the service processing method provided by the embodiment of the present disclosure, or send the service request submitted by the user and the preset service component library 106 to other terminal devices, servers, or server clusters, and execute the service processing method provided by the embodiment of the present disclosure by the other terminal devices, servers, or server clusters receiving the service request and the service component library 106.
It should be understood that the numbers of terminal devices, networks, servers, service components, service component libraries, and component lists in fig. 1 are merely illustrative. There may be any number of terminal devices, networks, servers, business components, business component libraries, and component lists, as desired for implementation.
Fig. 2 schematically shows a flow chart of a traffic processing method according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S210 to S240.
In operation S210, a service processing request for processing a service to be processed is obtained, where the service processing request includes a service scene identifier of the service to be processed.
In operation S220, in response to the service processing request, according to the service scenario identifier, a plurality of service components for processing the service to be processed are determined, where each service component is created according to the service logic.
In operation S230, an execution order of the plurality of business components is determined.
In operation S240, a plurality of service components are called according to the execution order to process the service to be processed.
According to the embodiment of the disclosure, the service scene identifier may be a unique identifier for one service process in the service system, and after a new service processing request is received, the service scene identifier in the new service processing request and the service scene identifier stored in the server may be matched to extract the plurality of service components corresponding to the service scene identifier and the execution sequence among the plurality of service components.
According to the embodiment of the disclosure, the execution sequence among the service components may include an execution sequence among each service step in the service flow and an execution sequence of the service components in each service step, where the execution sequence may include serial, parallel, selective, and the like, and the execution sequence may be edited in advance by a developer and stored in a data structure corresponding to the service scene identifier in the server.
According to the embodiment of the disclosure, the execution sequence between the service components can be compiled by adopting a data exchange language, such as XML, JSON and the like.
According to the embodiment of the disclosure, the service components may be obtained by encapsulating all service logics to be executed in a service into a standard service block by research and development personnel, and each service component may operate as an independent node.
According to an embodiment of the present disclosure, the service component may be implemented by compiling in a plurality of programming languages, including but not limited to Javascript, C, JAVA, and the like.
For example, in the internet medical service, a plurality of inquiry flows may be included, including a quick inquiry flow, an emergency inquiry flow, an appointment inquiry flow, and the like, where the flow name of the inquiry flow is used as a service scene identifier of the inquiry flow. After receiving a rapid inquiry service request sent by a user, specific steps of the rapid inquiry process can be called from a server through a service scene identifier of the rapid inquiry process, the steps comprise parameter check, supplement request parameters and the like, and the steps are executed in a serial sequence. In each specific step, a plurality of service components may be included, for example, the service components executed in series by the four service parameter checking, pin attribute checking, sku information checking, and information source judging steps in the parameter checking step.
According to the embodiment of the disclosure, after a service processing request is received, the execution sequence of a plurality of service components and the execution sequence of the plurality of service components for processing the service to be processed are determined according to the service scene identification, and the plurality of service components are called according to the execution sequence to process the service to be processed. Because the mode of separating the service components from the execution sequence is adopted, different service requests can be met by adjusting the execution sequence and the related specific service components, and the service components can be multiplexed, thereby effectively reducing code redundancy and improving code multiplexing rate.
The method shown in fig. 2 is further described with reference to fig. 3-8 in conjunction with specific embodiments.
Fig. 3 schematically shows a schematic diagram of business components included in a business system according to an embodiment of the present disclosure.
As shown in fig. 3, the illustrated service components are part of the service components used in the internet medical service system of the embodiment of the present disclosure.
According to embodiments of the present disclosure, a service component may be a standard service block, may operate as an independent node, and may implement a fixed logic. For example, after the service component of checking the pin attribute is executed, a pin attribute checking result of the target user can be obtained, and in the application scenario of this embodiment, the target user may be a doctor or a patient.
According to the embodiment of the disclosure, the repeated use of the same service component by a plurality of service processes can be realized by splitting and packaging the service logic into the service components, the reuse rate of service codes in the service components is effectively improved, and the number of the repeated redundant codes is reduced by more than 60%; meanwhile, the adoption of the service assembly enables the whole test range to be more definite, effectively improves the test coverage rate and reduces unnecessary workload.
Fig. 4 schematically shows a structural diagram of a business component according to an embodiment of the present disclosure.
As shown in fig. 4, each service component identifies a minimum service unit, and each service unit may implement a fixed logic. Based on the consideration of reducing the development and understanding cost of the business components and the design mode of the responsibility chain, the contents which are irrelevant to the business can be packaged into abstract classes in an inheritance mode, and the contents which are difficult to understand are written into the bottom layer of the program in a template mode.
According to the embodiment of the disclosure, the structure of each business component comprises a component parent class, a component template class and a component implementation class.
According to embodiments of the present disclosure, a component parent class may be a class that characterizes the interface that needs to be called to process business logic. Specifically, the component parent class may define the interface of the business component by including a standard class provided in the compilation environment and by means of interface definitions in the standard class. Taking a service component based on C + + compilation as an example, the component parent may be an abstract class that includes header files such as an iostream, defines the interface data type, and encapsulates the content that is not related to the specific service.
According to an embodiment of the present disclosure, a component template class may be a class that characterizes the ability to provide common functionality, where the common functionality may be derived from analyzing business logic.
According to embodiments of the present disclosure, the component template class may be derived by creating a common flow, creating a common, and creating flow logic. The common flow can be a common flow for representing and processing business logic, such as common input statements and output statements in a program language; the business template can be a common tool required for characterizing the processing business logic, such as if, while, switch, for and the like in the program language are used for characterizing the logic relationship; the process logic may be an order in which the individual processes included in the process business logic are characterized, and the component template class is completed by combining the common processes and the common tools in the order of the processes.
According to an embodiment of the present disclosure, a component implementation class may be a class that characterizes the executable business logic for implementing specific business functions.
According to the embodiment of the disclosure, the component template class and the component parent class, and the component implementation class and the component template class can be connected in an inheritance manner. Taking a JAVA compilation based business component as an example, the component template class B may inherit the function and interface of the component parent class a through an inheritance statement, which may be denoted as public class B extensions a.
According to embodiments of the present disclosure, different business components may have the same component parent and component template class. For example, the two service components, i.e., the pin attribute verification component and the sku information verification component, represent two different component implementation classes, and can respectively implement verification on the pin attribute and the sku information. The two business components may have the same component template class and component parent class. The component template class can be an information verification class, and can verify the received information to be verified and output a verification result. The data types of the input interface and the output interface are defined in the component parent class, wherein the input interface can receive the character string for representing the information to be verified and the character string for representing the information dictionary of the information to be verified, and the output interface can output the Boolean value for representing the checking result.
According to the embodiment of the disclosure, the compiling difficulty of the service component is effectively reduced and the bottom layer research and development coding speed is improved by means of inheriting the component parent class or the component template class.
FIG. 5 schematically shows a schematic diagram of a business process according to an embodiment of the disclosure.
As shown in fig. 5, the illustrated business process is a schematic diagram of a rapid inquiry process in the internet medical business system according to the embodiment of the present disclosure.
According to the embodiment of the disclosure, for the service scene identifier of the rapid inquiry flow, the preset flow comprises the following steps: parameter checking, request parameter supplementing, physician information obtaining, patient information obtaining, inquiry sheet parameter constructing, inquiry sheet establishing, middle platform order parameter constructing, business operation before order placing, middle platform order issuing, business operation after order placing and unnecessary compensation logic constructing, wherein all the steps are executed in sequence in a serial execution mode.
FIG. 6 is a schematic diagram that schematically illustrates logical relationships between business components in a business step, according to an embodiment of the disclosure.
As shown in fig. 6, the illustrated logical relationship between the business components is used to characterize the logical relationship between the business components corresponding to each step in the rapid inquiry flow in the internet medical business system according to the embodiment of the present disclosure.
According to the embodiment of the disclosure, each step in the rapid inquiry flow can be realized by a plurality of business components according to a preset component execution sequence.
For example, in the parameter checking step, the four service components of service parameter checking, pin attribute checking, sku information checking and information source judgment are sequentially executed according to a serial sequence; in the step of supplementing request parameters, three service components, namely right information acquisition, medicine source setting and service scene modification according to departments, are used as a first queue to be executed in series, two service components, namely HTML injection prevention and service type confirmation, are used as a second queue to be executed in series, and the first queue and the second queue are executed in parallel; in the acquiring of the doctor information step, only the business component acquiring the doctor information is executed.
According to the embodiment of the present disclosure, in other steps, the plurality of business components may also be executed in other logical orders than serial and parallel, such as condition, selection, loop, and the like. The execution sequence of the service components in the embodiments of the present disclosure may be freely configured as needed, and is not limited herein.
According to the embodiment of the disclosure, through arrangement and configuration of the business components, 0 development and configuration aiming at business requirements are realized, the online times are reduced, and the online risk is reduced.
Fig. 7 schematically shows a schematic diagram of a business process flow according to another embodiment of the present disclosure.
As shown in fig. 7, the business process flow includes operations S701 to S707.
In operation S701, a first service component is called from the component list according to the execution order.
In operation S702, a first business component is executed.
In operation S703, an execution result of the first service component is determined. In case that it is determined that the execution result of the first business component is successful, performing operation S704; in case that it is determined that the execution result of the first business component is an execution failure, operation S707 is performed.
In operation S704, the first business component is deleted from the component list.
In operation S705, it is determined whether the component list is empty. In case it is determined that the component list is not empty, performing operation S706; and in the case that the component list is determined to be empty, ending the business processing flow.
In operation S706, a second service component is called from the component list according to the execution order and executed according to the method of operation S702 until the component list is empty.
In operation S707, it is confirmed whether to be re-executed. In case it is determined to re-execute the first business component, the method of operation S702 is performed to re-execute the first business component; and in the case of refusing to execute the first business component again, ending the business processing flow.
According to the embodiment of the disclosure, a plurality of service components determined by the service scene identifier may be stored in the component list, and the processing of the service to be processed may be completed by calling the service components in the component list according to the execution order.
Fig. 8 schematically shows a schematic diagram of a data structure of a service execution order according to an embodiment of the present disclosure.
As shown in fig. 8, in the embodiment of the present disclosure, the service execution sequence corresponding to the service scene identifier may be preset by using a JSON statement, and when the embodiment is used, the main program may invoke the process execution to execute all service components according to the preset service execution sequence by parsing the arranged JSON string.
For example, taking a bill extraction flow as an example, after receiving the request, submitOrder of the bill extraction template may be called to obtain data representing the service execution flow, determine data used for representing the service component corresponding to the service scene identifier, and write the data into the memory. Then, each service component (business unit) can be instantiated into an object by a doc (business context, configKey) method, and written into the component list according to a preset execution sequence, and the business components are sequentially executed by using a ding method to complete the whole service.
According to the embodiment of the present disclosure, the service execution order may also be defined using other programming languages, such as XML, and may also be implemented using different data structures.
Fig. 9 schematically shows a block diagram of a traffic processing device according to an embodiment of the present disclosure.
As shown in fig. 9, the service processing apparatus includes an obtaining module 910, a first determining module 920, a second determining module 930, and a processing module 940.
The obtaining module 910 is configured to obtain a service processing request for processing a service to be processed, where the service processing request includes a service scene identifier of the service to be processed.
A first determining module 920, configured to determine, in response to a service processing request, a plurality of service components for processing a service to be processed according to a service scenario identifier, where each service component is created according to a service logic.
A second determining module 930, configured to determine an execution order of the plurality of business components.
And the processing module 940 is configured to call the plurality of service components according to the execution sequence to process the service to be processed.
According to the embodiment of the disclosure, after a service processing request is received, the execution sequence of a plurality of service components and the execution sequence of the plurality of service components for processing the service to be processed are determined according to the service scene identification, and the plurality of service components are called according to the execution sequence to process the service to be processed. Because the mode of separating the service components from the execution sequence is adopted, different service requests can be met by adjusting the execution sequence and the related specific service components, and the service components can be multiplexed, thereby effectively reducing code redundancy and improving code multiplexing rate.
According to the embodiment of the disclosure, the service processing apparatus further includes a creation module, and the creation module includes a first creation unit, a second creation unit, a third creation unit, and a fourth creation unit.
Wherein:
the first creating unit is used for creating a component parent class, wherein the component parent class is a class for representing an interface required to be called for processing the business logic.
And the second creating unit is used for creating a component template class, wherein the component template class is a class which is characterized by being capable of providing a common function, and the common function is obtained by analyzing the business logic.
And the third creating unit is used for creating a component implementation class, wherein the component implementation class is a class which is characterized by being capable of executing business logic.
And the fourth creating unit is used for creating the service component according to the component parent class, the component template class and the component implementation class.
According to an embodiment of the present disclosure, the second creating unit includes a first creating sub-unit, a second creating sub-unit, a third creating sub-unit, and a fourth creating sub-unit. Wherein:
and the first creating subunit is used for creating a common flow, wherein the common flow is a common flow for characterizing and processing business logic.
And a second creating subunit, configured to create a common template, wherein the service template is a common tool required for characterizing the service logic.
And the third creating subunit is used for creating a flow logic, wherein the flow logic is the sequence of each flow included in the characterization processing business logic.
And the fourth creating subunit is used for creating the component template class according to the common flow, the common template and the flow logic.
According to the embodiment of the disclosure, the service processing device further comprises a storage module, and the storage module is used for storing the plurality of service components in the component list.
According to the embodiment of the present disclosure, the processing module 940 is further configured to call the service components in the component list according to the execution sequence to process the service to be processed.
According to an embodiment of the present disclosure, the processing module 940 includes a first processing unit, a second processing unit, a third processing unit, and a fourth processing unit. Wherein:
and the first processing unit is used for calling the first service component from the component list according to the execution sequence.
And the second processing unit is used for executing the first service assembly so as to process the processing service.
And the third processing unit is used for deleting the first service component from the component list.
And the fourth processing unit is used for finishing processing the service to be processed if the component list is determined to be empty under the condition that the execution result of the first service component is determined to be successful.
According to an embodiment of the present disclosure, the processing module 940 further includes a fifth processing unit. And the fifth processing unit is used for calling the second service component from the component list according to the execution sequence under the condition that the component list is determined not to be empty until the component list is determined to be empty.
According to an embodiment of the present disclosure, the processing module 940 further includes a sixth processing unit. The sixth processing unit is configured to, if it is determined that the execution result of the first service component is an execution failure, re-execute the first service component if it is determined that the first service component is re-executed.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented at least partially as a hardware Circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a Circuit, or implemented by any one of three implementations of software, hardware, and firmware, or any suitable combination of any of them. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any number of the obtaining module 910, the first determining module 920, the second determining module 930, and the processing module 940 may be combined to be implemented in one module/unit/sub-unit, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the disclosure, at least one of the obtaining module 910, the first determining module 920, the second determining module 930, and the processing module 940 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or may be implemented in any one of three implementations of software, hardware, and firmware, or in a suitable combination of any of them. Alternatively, at least one of the obtaining module 910, the first determining module 920, the second determining module 930, and the processing module 940 may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.
It should be noted that, the service processing apparatus portion in the embodiment of the present disclosure corresponds to the service processing method portion in the embodiment of the present disclosure, and the description of the service processing apparatus portion specifically refers to the service processing method portion, which is not described herein again.
Fig. 10 schematically shows a block diagram of an electronic device adapted to implement a traffic processing method according to an embodiment of the present disclosure. The electronic device shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 10, an electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001 that can perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. Processor 1001 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the present disclosure.
In the RAM 1003, various programs and data necessary for the operation of the electronic apparatus 1000 are stored. The processor 1001, ROM 1002, and RAM 1003 are connected to each other by a bus 1004. The processor 1001 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1002 and/or the RAM 1003. Note that the programs may also be stored in one or more memories other than the ROM 1002 and the RAM 1003. The processor 1001 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. The computer program performs the above-described functions defined in the system of the embodiment of the present disclosure when executed by the processor 1001. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable Computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM) or flash Memory), a portable compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the preceding. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 1002 and/or the RAM 1003 described above and/or one or more memories other than the ROM 1002 and the RAM 1003.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method provided by the embodiments of the present disclosure, when the computer program product is run on an electronic device, the program code being configured to cause the electronic device to implement the business processing method provided by the embodiments of the present disclosure.
The computer program, when executed by the processor 1001, performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via the communication part 1009, and/or installed from the removable medium 1011. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device through any of a variety of Networks, including Local Area Networks (LANs) or Wide Area Networks (WANs), or may be connected to external computing devices (e.g., through the internet using an internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.
Claims (11)
1. A service processing method comprises the following steps:
acquiring a service processing request for processing a service to be processed, wherein the service processing request comprises a service scene identifier of the service to be processed;
responding to the service processing request, and determining a plurality of service components for processing the service to be processed according to the service scene identification, wherein each service component is created according to service logic;
determining an execution order of the plurality of business components; and
and calling the plurality of service components according to the execution sequence to process the service to be processed.
2. The method of claim 1, wherein each of the business components is created according to business logic, comprising:
creating a component parent class, wherein the component parent class is a class for representing an interface required to be called for processing the business logic;
creating a component template class, wherein the component template class is a class which is characterized by being capable of providing a common function, and the common function is obtained by analyzing the business logic;
creating a component implementation class, wherein the component implementation class is a class that characterizes the business logic; and
and creating the service component according to the component parent class, the component template class and the component implementation class.
3. The method of claim 2, wherein the creating a component template class comprises:
creating a common flow, wherein the common flow is a common flow for characterizing and processing the business logic;
creating a common template, wherein the service template is a common tool required for characterizing the service logic;
creating flow logic, wherein the flow logic is used for representing and processing the sequence of each flow included in the business logic; and
and creating the component template class according to the common flow, the common template and the flow logic.
4. The method of any of claims 1-3, further comprising:
storing the plurality of business components in a component list;
the calling the plurality of service components according to the execution sequence to process the service to be processed includes:
and calling the service components in the component list according to the execution sequence so as to process the service to be processed.
5. The method of claim 4, wherein the invoking the service components in the component list according to the execution order to process the service to be processed comprises:
calling a first service component from the component list according to the execution sequence;
executing the first business component to process the processing business;
deleting the first business component from the component list; and
and under the condition that the execution result of the first service component is determined to be successful, if the component list is determined to be empty, finishing processing the service to be processed.
6. The method of claim 5, further comprising:
and if the component list is determined not to be empty, calling a second service component from the component list according to the execution sequence until the component list is determined to be empty.
7. The method of claim 5, further comprising:
and under the condition that the execution result of the first business component is determined to be the execution failure, if the first business component is determined to be executed again, the first business component is executed again.
8. A traffic processing apparatus, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a service processing request for processing a service to be processed, and the service processing request comprises a service scene identifier of the service to be processed;
a first determining module, configured to determine, in response to the service processing request, a plurality of service components for processing the service to be processed according to the service scene identifier, where each service component is created according to a service logic;
a second determining module, configured to determine an execution order of the plurality of business components; and
and the processing module is used for calling the plurality of service components according to the execution sequence so as to process the service to be processed.
9. An electronic device, comprising:
one or more processors;
a memory for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-7.
10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 7.
11. A computer program product comprising a computer program which, when executed by a processor, is adapted to carry out the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469525.XA CN113110963A (en) | 2021-04-28 | 2021-04-28 | Service processing method, service processing device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469525.XA CN113110963A (en) | 2021-04-28 | 2021-04-28 | Service processing method, service processing device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113110963A true CN113110963A (en) | 2021-07-13 |
Family
ID=76720311
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110469525.XA Pending CN113110963A (en) | 2021-04-28 | 2021-04-28 | Service processing method, service processing device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113110963A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626102A (en) * | 2021-08-09 | 2021-11-09 | 北京奇艺世纪科技有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN113792093A (en) * | 2021-08-25 | 2021-12-14 | 通号城市轨道交通技术有限公司 | Signal system interface service creating and executing method, device and electronic equipment |
| CN114020345A (en) * | 2021-09-28 | 2022-02-08 | 湖南创星科技股份有限公司 | Medical affair configuration method and device, computer equipment and storage medium |
| CN114037422A (en) * | 2021-11-10 | 2022-02-11 | 中国建设银行股份有限公司 | Service processing method, system, device, electronic equipment and storage medium |
| CN114170015A (en) * | 2021-12-09 | 2022-03-11 | 中国工商银行股份有限公司 | Information processing method, system, device and medium |
| CN114296789A (en) * | 2022-03-09 | 2022-04-08 | 太平金融科技服务(上海)有限公司深圳分公司 | Business processing method, device, equipment and storage medium based on full-flow configuration |
| CN114461265A (en) * | 2021-12-24 | 2022-05-10 | 北京达佳互联信息技术有限公司 | Business processing method and device, electronic equipment and storage medium |
| CN115268283A (en) * | 2022-06-29 | 2022-11-01 | 青岛海尔科技有限公司 | Edge scene execution method and device, storage medium and electronic device |
| CN115564322A (en) * | 2022-12-06 | 2023-01-03 | 连连（杭州）信息技术有限公司 | Business processing method and device, electronic equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010139226A1 (en) * | 2009-05-31 | 2010-12-09 | 大连新中连软件集团有限公司 | Service component and application software development method and system based on the service component |
| CN107038042A (en) * | 2017-02-07 | 2017-08-11 | 阿里巴巴集团控股有限公司 | The method and device that a kind of business is performed |
| CN108958714A (en) * | 2018-07-02 | 2018-12-07 | 平安科技（深圳）有限公司 | Business component type development method and device, computer equipment and storage medium |
| CN109144479A (en) * | 2018-07-20 | 2019-01-04 | 中国邮政储蓄银行股份有限公司 | Development frame |
| CN109324787A (en) * | 2017-08-18 | 2019-02-12 | 深圳怡化电脑股份有限公司 | A kind of business software development approach, device and terminal device |
| CN112559095A (en) * | 2020-12-16 | 2021-03-26 | 微医云(杭州)控股有限公司 | Target service execution method, system, server and storage medium |
| CN112596871A (en) * | 2020-12-16 | 2021-04-02 | 中国建设银行股份有限公司 | Service processing method and device |
| CN112631590A (en) * | 2020-12-31 | 2021-04-09 | 北京字节跳动网络技术有限公司 | Component library generation method and device, electronic equipment and computer readable medium |
| CN112685091A (en) * | 2020-12-16 | 2021-04-20 | 平安国际融资租赁有限公司 | Service request processing method, device, equipment and medium based on big data |
-
2021
- 2021-04-28 CN CN202110469525.XA patent/CN113110963A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010139226A1 (en) * | 2009-05-31 | 2010-12-09 | 大连新中连软件集团有限公司 | Service component and application software development method and system based on the service component |
| CN107038042A (en) * | 2017-02-07 | 2017-08-11 | 阿里巴巴集团控股有限公司 | The method and device that a kind of business is performed |
| CN109324787A (en) * | 2017-08-18 | 2019-02-12 | 深圳怡化电脑股份有限公司 | A kind of business software development approach, device and terminal device |
| CN108958714A (en) * | 2018-07-02 | 2018-12-07 | 平安科技（深圳）有限公司 | Business component type development method and device, computer equipment and storage medium |
| CN109144479A (en) * | 2018-07-20 | 2019-01-04 | 中国邮政储蓄银行股份有限公司 | Development frame |
| CN112559095A (en) * | 2020-12-16 | 2021-03-26 | 微医云(杭州)控股有限公司 | Target service execution method, system, server and storage medium |
| CN112596871A (en) * | 2020-12-16 | 2021-04-02 | 中国建设银行股份有限公司 | Service processing method and device |
| CN112685091A (en) * | 2020-12-16 | 2021-04-20 | 平安国际融资租赁有限公司 | Service request processing method, device, equipment and medium based on big data |
| CN112631590A (en) * | 2020-12-31 | 2021-04-09 | 北京字节跳动网络技术有限公司 | Component library generation method and device, electronic equipment and computer readable medium |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626102A (en) * | 2021-08-09 | 2021-11-09 | 北京奇艺世纪科技有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN113792093A (en) * | 2021-08-25 | 2021-12-14 | 通号城市轨道交通技术有限公司 | Signal system interface service creating and executing method, device and electronic equipment |
| CN114020345A (en) * | 2021-09-28 | 2022-02-08 | 湖南创星科技股份有限公司 | Medical affair configuration method and device, computer equipment and storage medium |
| CN114020345B (en) * | 2021-09-28 | 2023-02-17 | 湖南创星科技股份有限公司 | Medical affair configuration method and device, computer equipment and storage medium |
| CN114037422A (en) * | 2021-11-10 | 2022-02-11 | 中国建设银行股份有限公司 | Service processing method, system, device, electronic equipment and storage medium |
| CN114170015A (en) * | 2021-12-09 | 2022-03-11 | 中国工商银行股份有限公司 | Information processing method, system, device and medium |
| CN114461265A (en) * | 2021-12-24 | 2022-05-10 | 北京达佳互联信息技术有限公司 | Business processing method and device, electronic equipment and storage medium |
| CN114296789A (en) * | 2022-03-09 | 2022-04-08 | 太平金融科技服务(上海)有限公司深圳分公司 | Business processing method, device, equipment and storage medium based on full-flow configuration |
| CN114296789B (en) * | 2022-03-09 | 2022-07-22 | 太平金融科技服务(上海)有限公司深圳分公司 | Business processing method, device, equipment and storage medium based on full-process configuration |
| CN115268283A (en) * | 2022-06-29 | 2022-11-01 | 青岛海尔科技有限公司 | Edge scene execution method and device, storage medium and electronic device |
| CN115564322A (en) * | 2022-12-06 | 2023-01-03 | 连连（杭州）信息技术有限公司 | Business processing method and device, electronic equipment and storage medium |
| CN115564322B (en) * | 2022-12-06 | 2023-09-19 | 连连（杭州）信息技术有限公司 | Service processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113110963A (en) | Service processing method, service processing device, electronic equipment and readable storage medium | |
| US11550599B2 (en) | Method and apparatus for running applet | |
| CN109951547B (en) | Transaction request parallel processing method, device, equipment and medium | |
| US20140026120A1 (en) | Unit testing an enterprise javabeans (ejb) bean class | |
| EP3989081A1 (en) | Method and device for publishing smart contract | |
| CN113132400B (en) | Business processing method, device, computer system and storage medium | |
| CN111736930B (en) | Program front-back end interface calling method and device, computer equipment and storage medium | |
| CN113191889A (en) | Wind control configuration method, configuration system, electronic device and readable storage medium | |
| CN113010561A (en) | Data acquisition method and device based on super account book and computer system | |
| CN110717992B (en) | Method, apparatus, computer system and readable storage medium for scheduling model | |
| CN117149248A (en) | Micro front end construction method, device, equipment and storage medium | |
| CN116302271A (en) | Page display method and device and electronic equipment | |
| CN114020414B (en) | Android system and bottom Linux symbiotic method and device, electronic equipment and storage medium | |
| CN113535565B (en) | Interface use case generation method, device, equipment and medium | |
| CN115033233A (en) | Interface calling method and device, electronic equipment and storage medium | |
| CN115277857A (en) | Method and device for interface verification, electronic equipment and storage medium | |
| CN112764729B (en) | Application software development method, device, computer equipment and readable storage medium | |
| CN114035864A (en) | Interface processing method, interface processing device, electronic device, and storage medium | |
| CN111158684B (en) | System creation method, device, electronic equipment and readable storage medium | |
| CN113778631A (en) | Distributed transaction compensation method and device, electronic equipment and readable storage medium | |
| CN113760262A (en) | Task processing method, device, computer system and computer readable storage medium | |
| CN112817573B (en) | Method, apparatus, computer system, and medium for building a streaming computing application | |
| CN113760356B (en) | Differential configuration method, device, equipment and medium of program product | |
| CN115758026A (en) | Interaction method and device of application program and network page | |
| CN113254114A (en) | Operation method, device, equipment and storage medium of block chain system |
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 |