CN110442481B - Service processing method, service component container and electronic equipment - Google Patents
Service processing method, service component container and electronic equipment Download PDFInfo
- Publication number
- CN110442481B CN110442481B CN201910622082.6A CN201910622082A CN110442481B CN 110442481 B CN110442481 B CN 110442481B CN 201910622082 A CN201910622082 A CN 201910622082A CN 110442481 B CN110442481 B CN 110442481B
- Authority
- CN
- China
- Prior art keywords
- service
- processing
- preset
- sub
- module
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/301—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is a virtual computing platform, e.g. logically partitioned systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Hardware Redundancy (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application discloses a service component container, a service processing method and electronic equipment, wherein the service component container can comprise: the system comprises a monitoring module, a synchronous processing module and an asynchronous processing module, wherein the monitoring module can monitor the processing result of a service component carried by a service component container on a target service, trigger the synchronous processing module when monitoring that the processing result fails due to a preset fault, process a first sub-service which is not affected by the preset fault in the target service according to a first preset processing flow, record a second sub-service which is affected by the preset fault in the target service, and return a result of successfully processing the target service to a service calling party; and the asynchronous processing module can process the second sub-service in the target service according to a second preset processing flow after the preset fault is recovered to be normal, and set the processing state of the target service as successful after the processing is successful.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a service processing method, a service component container, and an electronic device.
Background
Micro-service architecture is widely used because of its ability to split a single application into multiple micro-services for development, where the micro-services are built around business functions, different micro-services can be written in different programming languages, and different micro-services can be deployed and extended independently with little centralized management. In micro-service architecture, a container carrying business components (which may be referred to as a business component container) is often used to implement micro-services.
However, when a temporary failure occurs in a service component itself or an external system on which the service component depends, the existing service component container lacks the capability of actively coping with and automatically adapting to the temporary failure, which results in failure of service processing and adverse effects on users.
Disclosure of Invention
The embodiment of the application provides a business processing method, a business component container and electronic equipment, which are used for actively coping with and automatically adapting to temporary faults of a business component or an external system on which the business component depends, improving the probability of successful processing of business and reducing adverse effects on users.
In order to solve the technical problems, the embodiment of the application is realized as follows:
in a first aspect, a business component container is provided, comprising: the device comprises a monitoring module, a synchronous processing module and an asynchronous processing module;
The monitoring module is used for monitoring the processing result of the business component carried by the business component container on the target business and triggering the synchronous processing module when the processing result fails due to a preset fault;
the synchronous processing module is used for processing a first sub-service in the target service according to a first preset processing flow, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service affected by the preset fault;
and the asynchronous processing module is used for processing the second sub-service in the target service according to a second preset processing flow after the preset fault is recovered to be normal, and setting the processing state of the target service to be successful after the processing is successful.
In a second aspect, a service processing method is provided and applied to a service component container, where the service component container includes a listening module, a synchronous processing module and an asynchronous processing module, and the method includes:
the processing result of the business component carried by the business component container to the target business is monitored through the monitoring module, and the synchronous processing module is triggered when the processing result is monitored to fail due to a preset fault;
Processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
and after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by the asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
In a third aspect, an electronic device is provided, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
a monitoring module monitors a processing result of the service component carried by the service component container on a target service, and triggers a synchronous processing module when the processing result is monitored to fail due to a preset fault;
Processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
and after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by an asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
In a fourth aspect, a computer-readable storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to:
a monitoring module monitors a processing result of the service component carried by the service component container on a target service, and triggers a synchronous processing module when the processing result is monitored to fail due to a preset fault;
Processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
and after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by an asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
The technical scheme provided by the embodiment of the application has at least one technical effect as follows: the service component container comprises a monitoring module, a synchronous processing module and an asynchronous processing module, wherein the monitoring module automatically triggers the synchronous processing module to process a first sub-service which is not affected by a preset fault in a target service and record a second sub-service which is affected by the preset fault in the target service when monitoring that the processing result of the target service fails due to the preset fault; and automatically processing a second sub-service in the target service after the preset fault is recovered to be normal through an asynchronous processing module, and setting the processing state of the target service to be successful after the processing is successful. Therefore, the method and the device can actively cope with and automatically adapt to the situation that the processing of the target service fails due to the preset fault, realize the successful processing of the target service, improve the probability of successfully processing the target service and reduce the adverse effect on users.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
fig. 1 is a schematic structural view of a service component container in the related art.
Fig. 2 is a schematic structural diagram of a service component container according to an embodiment of the present disclosure.
Fig. 3 is a schematic diagram of a synchronization process in a service processing procedure according to an embodiment of the present disclosure.
Fig. 4 is a schematic diagram of an asynchronous processing flow in a service processing procedure provided in an embodiment of the present disclosure.
Fig. 5 is a second schematic structural diagram of a service component container according to an embodiment of the present disclosure.
Fig. 6A is a schematic diagram of a sequential flow provided in an embodiment of the present disclosure.
Fig. 6B is a schematic diagram of a parallel flow provided in an embodiment of the present disclosure.
Fig. 6C is a schematic diagram of a branching flow provided in the embodiment of the present disclosure.
Fig. 7 is a third schematic structural diagram of a service component container according to an embodiment of the present disclosure.
Fig. 8 is an interaction timing diagram of a service processing method according to an embodiment of the present disclosure.
Fig. 9 is a schematic flow chart of a service processing method according to an embodiment of the present disclosure.
Fig. 10 is a second flowchart of a service processing method according to the embodiment of the present disclosure.
Fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
As shown in fig. 1, in the related art, a service component container 1 carries a service component 12, a network protocol conversion and deserialization module 11, and an external service call and serialization module 13. After receiving a service request (e.g., a processing request of a target service hereinafter), the service component container 1 performs network protocol conversion and/or deserialization by using the network protocol conversion and deserialization module 11; then, calling a local service component 12 to process the service request; then, the external service calling and serializing module 13 is utilized to generate an external service calling request and serialize 13, and then the external service calling request is sent to the external service 2 so as to realize the calling of the external service 2; finally, after receiving the processing state returned by the external service 2, the processing result of the service is fed back to the service calling party (user) which initiates the service request.
Although the service component container 1 shown in fig. 1 has better stability, after a preset fault occurs in the service component 12 itself or the external service 2 relied on by the service component 12, for example, after a Database (DB) fault occurs and an unknown temporary system fault such as network performance occurs, if the service processing procedure has timed out, a failed service processing result is returned to the service caller (user), so that the service request of the user is not successfully processed, and inconvenience is brought to the user. As can be seen, the service component container 1 in the related art lacks the capability of active handling and automatic adaptation when the service component 12 itself or an external system (such as the external service 2) on which the service component 12 depends has a temporary system failure, and cannot ensure that the service is successfully handled, thereby causing adverse effects to the user.
In order to solve the above problems, embodiments of the present disclosure provide a service component container, a service processing method, and an electronic device. As shown in fig. 6, the service component container 1 provided in the embodiment of the present specification may be deployed in a server 3 in a micro service architecture.
A service component container provided in an embodiment of the present disclosure is described below.
As shown in fig. 2, the service component container 1 provided in the embodiment of the present disclosure may further include, in addition to a service component 12, a network protocol conversion and deserialization module 11, and an external service invocation and serialization module 13: a listening module 14, a synchronous processing module 15 and an asynchronous processing module 16.
The monitoring module 14 is configured to monitor a processing result of the service component 12 carried by the service component container 1 on the target service, and trigger the synchronization processing module 15 when it is monitored that the processing result fails due to a preset failure.
The target service is the service requested to be processed by the service processing request received by the service component container 1. Taking the service component 12 carried by the service component container 1 as an example of a payment service supporting component, the target service may be a payment service in which the user pays the amount of consumption to the merchant.
Illustratively, the preset faults may include at least one of the following faults: a temporary system failure of the business component itself, and a temporary system failure of an external service on which the business component depends. Of course, in addition to these two temporary system failures, the preset failures may also be other types of failures (e.g., configuration errors of business rules, etc.). That is, the service component container 1 provided in the embodiment of the present specification can actively cope with other failures than the temporary system failures of the service component 12 itself and the external services on which the service component 12 depends.
Optionally, the monitoring module 14 may be configured to trigger the synchronization processing module 15 when the monitored processing result is failure and the target service meets a first preset trigger condition.
That is, in the embodiment of the present specification, the trigger synchronization processing module 15 may perform the failure autonomous handling only when the target service satisfying the first preset trigger condition is failed to be handled. The first preset trigger condition may be understood as an admission condition whether or not failure autonomous handling is performed.
Wherein the first preset trigger condition may include, but is not limited to, one or more of the following conditions: the type of the target service is a preset type, the service calling party belongs to the preset type, the generation time of the target service is within a preset time range, and the accumulated number of times the target service is processed is smaller than the preset number of times.
Specifically, taking the target service as an example of the payment service above, the first preset trigger condition may include one or more of the following conditions: whether the type of the target service is a preset type, whether the payment amount is within a preset amount range, whether the user is a user of a preset type, whether the payment time is within a preset time range, whether the accumulated number of times the target service is processed is smaller than a preset number of times, and the like.
The synchronization processing module 15 is configured to process a first sub-service in the target service according to a first preset processing flow, record a second sub-service in the target service, and return a result of successfully processing the target service to a service caller, where the first sub-service is a sub-service that is not affected by the preset fault, and the second sub-service is a sub-service that is affected by the preset fault.
Also taking the service component 12 carried by the service component container 1 as a payment service supporting component, the target service is a payment service for paying the consumption amount to the merchant by the user, and the first sub-service may be pre-deduction from the local account of the user, and the second sub-service may be final deduction from the online banking account (external service) of the user. In this way, if the available credit limit of the local account of the user (such as the available credit limit of the consumer credit opened by the local account of the user) is greater than the amount of the consumer paid to the merchant by the user, and the temporary performance failure does not occur in the payment service support component, the first sub-service is considered to be not affected by the preset failure, and a processing result of successfully processing the target service can be returned to the user after the payment from the local account is successful; if the network on which the user depends on the internet bank has a temporary system fault, the second sub-service is considered to be influenced by the preset fault, and the second sub-service needs to be temporarily recorded in a Database (DB) to wait for the asynchronous scheduling module to perform asynchronous scheduling processing.
It should be appreciated that the first sub-service and the second sub-service are different when the target service is different, and the above example is only one possible application example and should not be construed as limiting the target service, the first sub-service, and the second sub-service.
It can be understood that, after the monitoring module 14 monitors that the processing result of the service component 12 on the target service is failure, the synchronization processing module 15 immediately processes the first sub-service that is not affected by the preset failure in the target service, and returns a service processing manner of successfully processing the result of the target service to the service caller (user), so that the user can receive the result of successfully processing the target service within a short time (such as within a preset timeout time) after initiating the processing request of the target service, that is, the user can receive the result of successfully processing the target service in a near-synchronous manner after initiating the processing request of the target service, so that the process can be referred to as a synchronous processing process of the target service. The first preset processing flow may be designed in advance according to the services supported by the service component 12 and the target services, which is not particularly limited in this specification.
The procedure of synchronizing the processing target service and the first preset processing flow will be described below with reference to the example shown in fig. 3.
As shown in fig. 3, the synchronization process of the target service may include four parts of a service entry 31, a pre-process 32, a service process 33, and a system process 34.
The portion of the service portal 31 may include an input step 311 and an output step 312. Wherein, the inputting step 311 includes reading a processing request of the target service, and the outputting step 312 includes outputting a processing result of the target service.
The portion of the pre-treatment 32 may include a pre-treatment step 321. The pre-processing step 321 may specifically include performing network protocol conversion and deserialization on the read processing request of the target service, and performing decryption on the read processing request of the target service, if necessary.
The business process 33 steps may include an input process flow (In Chain) 333 and an output process flow (Out Chain) 334. The input process flow 333 and the output process flow 334 can be regarded as the first preset process flow described above.
Specifically, as shown in fig. 3, the input processing flow 333 may include performing rule verification on the first sub-service according to a preset verification rule 331 and/or obtaining relevant parameters of the first sub-service, processing the first sub-service according to a preset service processing logic 332, and so on. It will be appreciated that if the target service read in part by the input 311 in the service portal 31 includes N first sub-services, then the service processing may need to be performed N times and the service processing logic 332 corresponding to the different first sub-services may be different.
Specifically, as shown in fig. 3, the output processing flow 334 may include assembling and outputting the processing result of the first sub-service of the target service based on a preset template (e.g., templates 1 to N), and templates adopted for different first sub-services may be different.
Optionally, the traffic handling portion 33 may also include log records 336 and asynchronous notifications 335. Wherein the asynchronous notification 335 may be a notification to the asynchronous processing module 16 that the processing of the first sub-service in the target service is complete such that the asynchronous processing module 16 begins processing the second sub-service in the target service.
The system processing 34 steps may include an idempotent processing step 341, an internal traffic processing step 342, a buffer recording step 343, and a timeout processing step 345, among others. The step 345 of timeout processing includes determining whether the processing procedure of the target service is timeout according to a preset timeout time preset for processing the target service, if yes, ending the processing of the target service; the contents to be implemented in the idempotent processing step 341, the internal service processing step 342, and the buffer recording step 343 are referred to the related art, and will not be described in detail in this specification.
It will be appreciated that, through the synchronization processing procedure shown in fig. 3, the user may receive the result of successful processing of the target service within the preset timeout period from the time of initiating the processing request of the target service, that is, the user may receive the result of successful processing of the target service in a near-synchronous manner after initiating the processing request of the target service, so that the procedure may be referred to as a synchronization processing procedure of the target service.
And the asynchronous processing module 16 is configured to process the second sub-service in the target service according to a second preset processing flow after the preset fault is recovered to be normal, and set the processing state of the target service to be successful after the processing is successful.
Taking the above example (the service component 12 carried by the service component container 1 is a payment service supporting component, the target service is a payment service for paying the consumption amount to the merchant by the user, the first sub-service may be a pre-deduction from the local account of the user, the second sub-service may be a final deduction from the internet bank account of the user), after the temporary system fault of the network on which the internet bank of the user depends is recovered to be normal, the second sub-service in the target service may be processed according to a second preset processing flow, and after the processing is successful, the processing state of the target service is set to be successful.
Optionally, the asynchronous processing module 16 may be configured to process a second sub-service in the target service according to the second preset processing flow when a second preset trigger condition is satisfied and the preset failure returns to normal. The second preset trigger condition may include reaching a preset timing time or receiving a preset trigger instruction (for example, receiving an instruction of processing the second sub-service manually sent by the user).
Optionally, the asynchronous processing module 16 may be configured to process the second sub-service in the target service according to the second preset processing flow when the second preset trigger condition is met and the preset failure is recovered to be normal after the second sub-service in the target service fails to be processed. Alternatively, the number of times of processing may also be accumulated.
It can be appreciated that, when the second preset trigger condition is satisfied and the preset failure is recovered to be normal, the asynchronous processing module 16 processes the second sub-service in the target service without being limited by the timeout time of processing the target service, so this process may be referred to as an asynchronous processing process of the target service. The second preset process flow may be designed in advance according to the services supported by the service component 12 and the target services, which is not particularly limited in this specification.
The process of asynchronously processing the target service and the second preset processing flow are described below with reference to the example shown in fig. 4.
As shown in fig. 4, the asynchronous processing procedure of the target service may include three parts of a service portal 41, a service process 42, and a system process 43.
The portion of the service portal 41 may include: a timed trigger step 412 and/or a manual trigger step 411.
The timing triggering step 412 includes triggering a process of asynchronously processing the second sub-service in the target service when a preset timing time is reached.
The manual triggering step 411 includes triggering a process of asynchronously processing the second sub-service in the target service when receiving an instruction for manually processing the designated second sub-service sent by the user, such as receiving an instruction for manually designating to process a plurality of (e.g. 100) second sub-services by the user.
After the timing triggering step 412, the portion of the service portal 41 may further include: a splitting task step 413, which includes splitting the plurality of second sub-services to be processed into a plurality of groups containing less than a preset number (e.g. 100) of second sub-services, so as to process the second sub-services in units of groups in the next process.
After the split task step 413 or the manual trigger step 411, the portion of the service portal 41 may further include: a second sub-service reading step 414, which includes reading a set of second sub-services to be processed from the database.
The portion of business process 42 may include: sub-service processing step 421. Specifically, the sub-service processing step 421 may include the following sub-steps: asynchronous marking 4211, sub-service processing 4212 and processing result judgment 4213.
Asynchronous marking 4211 comprises setting a new identification for the read second sub-service based on the preset marking template 422. It can be understood that the asynchronous marking is performed on the second sub-service, so that the external service can treat the second sub-service as a brand new service, and the probability of successfully treating the second sub-service can be improved.
Sub-service processing 4212 comprises processing the second sub-service with the new identification.
The processing result judgment 4213 includes judging whether the processing of the second sub-service with the new identification is successful based on the preset check rule 423, and proceeding to step 431 and/or step 432.
The portion of system processing 43 may include: step 431 and/or step 432. Step 431 includes asynchronous state synchronization of the target service (e.g. after the second sub-service of the target service is successfully processed, setting the processing state of the target service to be successful), asynchronous processing times record of the second sub-service, and the like; step 432 includes logging, etc.
The service component container provided in the embodiments of the present disclosure, because the service component container carries a service component, further includes a monitoring module, a synchronous processing module, and an asynchronous processing module, where the monitoring module automatically triggers the synchronous processing module when monitoring that a processing result of a target service fails due to a preset fault, processes a first sub-service that is not affected by the preset fault in the target service, and records a second sub-service that is affected by the preset fault in the target service; and automatically triggering an asynchronous processing module, processing a second sub-service in the target service after the preset fault is recovered to be normal, and setting the processing state of the target service to be successful after the processing is successful. Therefore, the method and the device can actively cope with and automatically adapt to the situation that the processing of the target service fails due to the preset fault, realize the successful processing of the target service, improve the probability of successfully processing the target service and reduce the adverse effect on users.
Optionally, as shown in fig. 5, the service component container 1 provided in the embodiment of the present specification may further include a management module 17, in addition to the service component 12, the listening module 14, the synchronous processing module 15, and the asynchronous processing module 16.
A management module 17, which is configured to manage the listening module 14, the synchronous processing module 15 and the asynchronous processing module 16.
As an example, the management module 17 may be configured to define and inject the first preset trigger condition into the listening module 14, define and inject the first preset process flow into the synchronous processing module 15, and define and inject the second preset process flow into the asynchronous processing module 16.
Specific examples of the first preset trigger condition, the first preset processing flow, and the second preset processing flow may be referred to above, and will not be described repeatedly herein.
It should be noted that, the first preset processing flow and the second preset processing flow defined by the management module 17 may be any one of a sequential flow, a parallel flow, a branching flow, and the like. Fig. 6A, 6B, and 6C show schematic diagrams of sequential flow, parallel flow, and branching flow, respectively.
As shown in fig. 6A, the sequential flow refers to a flow that needs to be sequentially executed from step (1) to step (2) to step (3). As shown in fig. 6B, the parallel flow refers to a flow in which step (1), step (2), and step (3) can be simultaneously performed in parallel. As shown in fig. 6C, the branching flow is a mixture of parallel flow and sequential flow, that is, part of the steps (e.g., step (2) and step (3)) that can be performed by the flow may be performed in parallel, and part of the steps need to be performed sequentially (e.g., step (3) and step (4)).
Further, the management module 17 may be further configured to schedule at least one of the first preset process flow and the second preset process flow based on preset rules.
Wherein the preset rules include at least one of the following rules: synchronous serial execution rules, asynchronous parallel execution rules, timing execution rules, loop execution rules, execution exception handling rules, transaction operation rules, condition judgment rules, external service call frequency control rules, external service call frequency accumulation rules, state retention rules, and the like. It will be appreciated that these rules may be flexibly set and are not limited to those listed in this specification.
Further, in order to make the first preset process flow and the second preset process flow defined by the management module 17 as lightweight as possible, the management module 17 may use a Web orchestration description language (Web Services Choreography Description Language, WS-CDL) to orchestrate the first preset process flow and the second preset process flow.
Furthermore, in order for business component container 1 to be a lightweight container, management module 17 may also employ WS-CDL to orchestrate the script of the synchronous process flow shown in FIG. 3 and the asynchronous process flow shown in FIG. 4. The following is one example of a script for the synchronous process flow shown in FIG. 3 and the asynchronous process flow shown in FIG. 4 employing WS-CDL orchestration:
the process arrangement implemented by the script is to synchronously and sequentially inquire the reverse Order (reverse Buy Order), specifically assemble the inquiry result into the request of Order placing (space Buy Order), circularly call the service component, assemble the operation result and then return to the user client, and finally asynchronously call the Order confirmation (Confirm Buy Order) to operate and synchronize the state. It will be appreciated that service invocation requests and context transfer may be accomplished by transferring scripts and execution states between different service component containers (invoking downstream service services from upstream services through markup).
Optionally, as shown in fig. 7, the service component container 1 provided in the embodiment of the present specification may further include a log component 18, a performance monitoring module 19, and a service management module 20, in addition to the service component 12, the listening module 14, the synchronous processing module 15, the asynchronous processing module 16, and the management module 17.
Wherein the log component 18 is operative to record a business process log; the performance monitoring module 19 may be configured to monitor performance of the service component container 1, such as stability, service processing success rate, etc.; the service management module 20 may be used to manage services supported by the service components 12, and so on.
In summary, in the service component container 1 of the embodiment of the present disclosure, a preset fault occurring in a target service processing process may be actively perceived by the monitoring module 14, and after the preset fault is perceived, the synchronous processing module 15 and the asynchronous processing module 16 are actively triggered to perform asynchronous processing on the target service, so that the probability of successful processing of the target service may be improved, and the influence on user experience is reduced. In addition, the management module 17 can be adopted to arrange the business processing flow in the business component container 1 in the form of script, so that the lightweight adaptive business processing scheme can be customized.
The foregoing describes a business component container provided in the present specification, and the following describes an interaction procedure of the business processing method provided in the present specification with reference to fig. 8.
As shown in fig. 8, a service processing method provided in the embodiment of the present disclosure includes:
Step 801, the service caller (user) 4 initiates a processing request for the target service to the service component container 1.
In step 802, the network protocol conversion and deserialization module 11 performs pre-processing, such as network protocol conversion and deserialization, on the received service request.
Step 803, the service component 12 performs internal service processing for the target service.
Step 804, the business component 12 invokes the external service 2 to process the target business.
Step 805, the external service 2 fails to process the target service due to a temporary system failure.
Step 806, the external service 2 returns the result of the processing failure to the business component 12.
In step 807, the monitoring module 14 monitors that the processing result of the service component 12 on the target service is failure, and determines that the target service meets the first preset triggering condition, and triggers the synchronization processing module 15.
Step 808, the synchronization processing module 15 processes a first sub-service in the target service according to a first preset processing flow, where the first sub-service is a sub-service that is not affected by the preset fault.
Step 809, the synchronization processing module 15 records the processing log of the target service.
Step 810, the synchronization processing module 15 returns the result of successfully processing the target service to the service caller 4.
In step 811, the asynchronous processing module 16 processes the second sub-service in the target service according to the second preset processing flow, and sets the processing state of the target service to be successful.
Step 812, after the preset failure returns to normal, the asynchronous processing module 16 initiates a request to the external service 2 to process the second sub-service in the target service.
Step 813, the external service 2 processes the second sub-service in the target service, and sets the processing state of the target service to be successful locally in the external service 2.
Step 814, the external service 814 returns the result of successfully processing the second sub-service in the target service to the asynchronous processing module.
In addition, as shown in fig. 9, the embodiment of the present disclosure further provides a service processing method, which may be applied to the service component container 1 provided in the embodiment of the present disclosure, where the service component container 1 may include a listening module, a synchronous processing module, and an asynchronous processing module, and on the basis of this, the method may include:
and 902, monitoring a processing result of the service component carried by the service component container on the target service through the monitoring module, and triggering the synchronous processing module when monitoring that the processing result fails due to a preset fault.
As an example, the preset faults may include at least one of the following faults: the system failure of the business component itself, and the system failure of the external service on which the business component depends. Of course, in addition to these two temporary system failures, the preset failures may also be other types of failures (e.g., configuration errors of business rules, etc.). That is, the service processing method provided in the embodiment of the present disclosure may also actively cope with other faults than the temporary system faults of the service component itself and the external service on which the service component depends.
Further, as another example, step 902 may specifically include: and triggering the synchronous processing module when the monitoring module monitors that the processing result is failure and the target service meets a first preset triggering condition.
Wherein the first preset trigger condition may include, but is not limited to, one or more of the following conditions: the type of the target service is a preset type, the service calling party belongs to the preset type, the generation time of the target service is within a preset time range, and the accumulated number of times the target service is processed is smaller than the preset number of times.
Step 904, processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service caller, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault.
Step 906, when the preset fault is recovered to be normal, processing, by the asynchronous processing module, a second sub-service in the target service according to a second preset processing flow, and setting a processing result of the target service to be successful after the processing is successful.
Optionally, step 906 may include: and when a second preset triggering condition is met and the preset fault is recovered to be normal, processing a second sub-service in the target service according to the second preset processing flow through the asynchronous processing module. The second preset triggering condition comprises reaching preset time or receiving a preset triggering instruction. Alternatively, the number of times of processing may also be accumulated.
The second preset processing flow includes: setting a new identifier for the second sub-service based on a preset marking template; the second sub-service with the new identity is processed.
According to the service processing method provided by the embodiment of the specification, as the processing result of the target service can be monitored through the monitoring module, and when failure caused by the preset fault is monitored in the processing result of the target service, the synchronous processing module is automatically triggered, the first sub-service which is not affected by the preset fault in the target service is processed, and the second sub-service which is affected by the preset fault in the target service is recorded; and after the preset fault is recovered to be normal, automatically processing a second sub-service in the target service through an asynchronous processing module, and setting the processing state of the target service to be successful after the processing is successful. Therefore, the method and the device can actively cope with and automatically adapt to the situation that the processing of the target service fails due to the preset fault, realize the successful processing of the target service, improve the probability of successfully processing the target service and reduce the adverse effect on users.
Optionally, the service component container may further include a management module, on the basis of which, as shown in fig. 10, a service processing method provided in the embodiment of the present disclosure may further include:
Step 908, managing, by the management module, the listening module, the synchronous processing module, and the asynchronous processing module.
As an example, step 908 may specifically include: and injecting the first preset triggering condition into the monitoring module, the first preset processing flow into the synchronous processing module and the second preset processing flow into the asynchronous processing module through the management module.
Further, the method shown in fig. 10 may further include: and arranging at least one of the first preset processing flow and the second preset processing flow based on preset rules through the management module.
It should be noted that, the first preset processing flow and the second preset processing flow defined by the management module may be any one of a sequential flow, a parallel flow, a branching flow, and the like.
Wherein the preset rules include at least one of the following rules: synchronous serial execution rules, asynchronous parallel execution rules, timing execution rules, loop execution rules, execution exception handling rules, transaction operation rules, condition judgment rules, external service call frequency control rules, external service call frequency accumulation rules, state retention rules, and the like.
Further, in order to make the first preset process flow and the second preset process flow defined by the management module 17 as lightweight as possible, WS-CDL may be used to schedule the first preset process flow and the second preset process flow.
In summary, according to the service processing method in the embodiments of the present disclosure, the monitoring module 14 may actively sense a preset fault occurring in the target service processing process, and after sensing the preset fault, actively trigger the synchronous processing module 15 and the asynchronous processing module 16 to perform asynchronous processing on the target service, so that the probability of successful processing of the target service may be improved, and the influence on user experience may be reduced. In addition, the management module 17 can be adopted to arrange the business processing flow in the business component container 1 in the form of script, so that the lightweight adaptive business processing scheme can be customized.
It should be noted that, since the service processing method may be applied to the service component container 1 shown in fig. 2, 5 or 7, the description of the service processing method in this embodiment of the present disclosure is simpler, and the relevant portions may refer to the description of the service component container 1 above, which is not repeated herein.
Fig. 11 is a schematic structural view of an electronic device according to an embodiment of the present disclosure. Referring to fig. 11, at the hardware level, the electronic device includes a processor, and optionally an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, network interface, and memory may be interconnected by an internal bus, which may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 11, but not only one bus or type of bus.
And the memory is used for storing programs. In particular, the program may include program code including computer-operating instructions. The memory may include memory and non-volatile storage and provide instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program, and a service component container is formed on a logic level, wherein the service component container comprises a monitoring module, a synchronous processing module and an asynchronous processing module. The processor is used for executing the programs stored in the memory and is specifically used for executing the following operations:
A monitoring module monitors a processing result of the service component carried by the service component container on a target service, and triggers a synchronous processing module when the processing result is monitored to fail due to a preset fault;
processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
and after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by an asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
The service processing method disclosed in the embodiment shown in fig. 9 or fig. 10 of the present specification may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also 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. The various methods, steps, and logic blocks disclosed in one or more embodiments of the present description may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with one or more embodiments of the present disclosure may be embodied directly in a hardware decoding processor or in a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
The electronic device may further execute the service processing method of fig. 9 or fig. 10, which is not described herein.
Of course, in addition to the software implementation, the electronic device in this specification does not exclude other implementations, such as a logic device or a combination of software and hardware, that is, the execution subject of the following process is not limited to each logic unit, but may also be hardware or a logic device.
The present description also proposes a computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of application programs, enable the portable electronic device to perform the method of the embodiment of fig. 9, and in particular to perform the following operations:
a monitoring module monitors a processing result of the service component carried by the service component container on a target service, and triggers a synchronous processing module when the processing result is monitored to fail due to a preset fault;
processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
And after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by an asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
The foregoing describes certain embodiments of the present disclosure, other embodiments being within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments in part.
In summary, the foregoing description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of one or more embodiments of the present disclosure, is intended to be included within the scope of one or more embodiments of the present disclosure.
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. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
Claims (18)
1. A business component container comprising: the device comprises a monitoring module, a synchronous processing module and an asynchronous processing module;
the monitoring module is used for monitoring the processing result of the business component carried by the business component container on the target business and triggering the synchronous processing module when the processing result is monitored to fail due to a preset fault;
The synchronous processing module is used for processing a first sub-service in the target service according to a first preset processing flow, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service affected by the preset fault;
and the asynchronous processing module is used for processing the second sub-service in the target service according to a second preset processing flow after the preset fault is recovered to be normal, and setting the processing state of the target service to be successful after the processing is successful.
2. The business component container of claim 1,
the preset faults include at least one of the following faults:
a temporary system failure of the business component itself, and
temporary system failures of external services on which the business components depend.
3. The business component container of claim 1,
the monitoring module is used for triggering the synchronous processing module when the monitored processing result is failure and the target service meets a first preset triggering condition;
Wherein the first preset trigger condition includes one or more of the following conditions:
the type of the target service is a preset type,
the service invoker belongs to a preset type,
the generation time of the target service is within a preset time range, and
the accumulated times of the processed target service is smaller than the preset times.
4. The business component container of claim 3,
the asynchronous processing module is used for processing a second sub-service in the target service according to the second preset processing flow when a second preset triggering condition is met and the preset fault is recovered to be normal;
the second preset triggering condition comprises reaching preset time or receiving a preset triggering instruction.
5. The business component container of claim 3, further comprising:
and the management module is used for managing the monitoring module, the synchronous processing module and the asynchronous processing module.
6. The business component container of claim 5,
the management module is configured to inject the first preset trigger condition into the monitoring module, inject the first preset processing flow into the synchronous processing module, and inject the second preset processing flow into the asynchronous processing module.
7. The business component container of claim 6,
the management module is further configured to schedule at least one of the first preset processing flow and the second preset processing flow based on a preset rule;
wherein the preset rules include at least one of the following rules: synchronous serial execution rule, asynchronous parallel execution rule, timing execution rule, loop execution rule, execution exception handling rule, transaction operation rule, condition judgment rule, external service call frequency control rule, external service call frequency accumulation rule and state retention rule.
8. The business component container of any of claims 1-7,
the first preset processing flow comprises the following steps: an input processing flow and an output processing flow;
the input processing flow comprises the following steps: performing rule verification on a first sub-service according to a preset verification rule, acquiring related parameters of the first sub-service, and processing the first sub-service according to a preset service processing logic;
the output processing flow comprises: and assembling and outputting the processing result of the first sub-service of the target service based on a preset template.
9. The business component container of any of claims 1-7,
The second preset processing flow includes:
setting a new mark for the second sub-service based on a preset marking template;
and processing the second sub-service provided with the new identifier.
10. A service processing method applied to a service component container, wherein the service component container comprises a monitoring module, a synchronous processing module and an asynchronous processing module, and the method comprises the following steps:
the processing result of the business component carried by the business component container to the target business is monitored through the monitoring module, and the synchronous processing module is triggered when the processing result is monitored to fail due to a preset fault;
processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
and after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by the asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
11. The method according to claim 10,
the preset faults include at least one of the following faults:
system failure of the business component itself, and
the business component relies on the system failure of the external service.
12. The method according to claim 10,
the monitoring module monitors a processing result of the service component carried by the service component container on the target service, and triggers the synchronous processing module when monitoring that the processing result fails due to a preset fault, including:
triggering the synchronous processing module when the monitored processing result is failure and the target service meets a first preset triggering condition;
wherein the first preset trigger condition includes one or more of the following conditions:
the type of the target service is a preset type,
the service invoker belongs to a preset type,
the generation time of the target service is within a preset time range, and
the accumulated times of the processed target service is smaller than the preset times.
13. The method according to claim 12,
the processing, by the asynchronous processing module, the second sub-service in the target service according to a second preset processing flow includes:
When a second preset triggering condition is met and the preset fault is recovered to be normal, processing a second sub-service in the target service according to the second preset processing flow through the asynchronous processing module;
the second preset triggering condition comprises reaching preset time or receiving a preset triggering instruction.
14. The method according to claim 12,
the business component container further comprises a management module, and the method further comprises:
and the monitoring module, the synchronous processing module and the asynchronous processing module are managed through the management module.
15. The method according to claim 14,
wherein, through the management module, manage the monitoring module, the synchronous processing module and the asynchronous processing module, including:
and injecting the first preset triggering condition into the monitoring module, the first preset processing flow into the synchronous processing module and the second preset processing flow into the asynchronous processing module through the management module.
16. The method of claim 15, further comprising:
arranging, by the management module, at least one of the first preset process flow and the second preset process flow based on preset rules;
Wherein the preset rules include at least one of the following rules: synchronous serial execution rule, asynchronous parallel execution rule, timing execution rule, loop execution rule, execution exception handling rule, transaction operation rule, condition judgment rule, external service call frequency control rule, external service call frequency accumulation rule and state retention rule.
17. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
the method comprises the steps of monitoring a processing result of a service component carried by a service component container to a target service through a monitoring module, and triggering a synchronous processing module when the processing result fails due to a preset fault;
processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
And after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by an asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
18. A computer-readable storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to:
the method comprises the steps of monitoring a processing result of a service component carried by a service component container to a target service through a monitoring module, and triggering a synchronous processing module when the processing result is monitored to fail due to a preset fault;
processing a first sub-service in the target service according to a first preset processing flow by the synchronous processing module, recording a second sub-service in the target service, and returning a result of successfully processing the target service to a service calling party, wherein the first sub-service is a sub-service which is not affected by the preset fault, and the second sub-service is a sub-service which is affected by the preset fault;
And after the preset faults are recovered to be normal, processing a second sub-service in the target service according to a second preset processing flow by an asynchronous processing module, and setting the processing result of the target service as success after the processing is successful.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910622082.6A CN110442481B (en) | 2019-07-10 | 2019-07-10 | Service processing method, service component container and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910622082.6A CN110442481B (en) | 2019-07-10 | 2019-07-10 | Service processing method, service component container and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110442481A CN110442481A (en) | 2019-11-12 |
| CN110442481B true CN110442481B (en) | 2023-09-22 |
Family
ID=68430094
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910622082.6A Active CN110442481B (en) | 2019-07-10 | 2019-07-10 | Service processing method, service component container and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110442481B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111142867B (en) * | 2019-12-31 | 2024-04-02 | 谷云科技(广州)有限责任公司 | Service visual arrangement system and method under micro service architecture |
| CN111290866B (en) * | 2020-02-11 | 2023-06-30 | 支付宝(杭州)信息技术有限公司 | Service processing method and device |
| CN111552459B (en) * | 2020-04-16 | 2023-04-28 | 重庆富民银行股份有限公司 | Service arrangement flow management system and method |
| CN111737055A (en) * | 2020-06-23 | 2020-10-02 | 北京同邦卓益科技有限公司 | Service processing method, device, equipment and computer readable storage medium |
| CN113065967A (en) * | 2021-05-18 | 2021-07-02 | 中国农业银行股份有限公司 | Multi-mode service processing method, device and equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101593387A (en) * | 2008-05-27 | 2009-12-02 | 中国移动通信集团公司 | A kind of method, system and equipment that uses local account to carry out remote payment |
| CN106603708A (en) * | 2016-12-30 | 2017-04-26 | 中国建设银行股份有限公司 | Business processing method and device |
| CN106648936A (en) * | 2016-12-29 | 2017-05-10 | Tcl集团股份有限公司 | Cooperative processing method and system based on microservices and server |
| CN107038025A (en) * | 2016-09-28 | 2017-08-11 | 阿里巴巴集团控股有限公司 | System call method and device based on SOA framework |
| CN107153649A (en) * | 2016-03-02 | 2017-09-12 | 阿里巴巴集团控股有限公司 | A kind of data back up method and device |
| CN107193663A (en) * | 2017-01-04 | 2017-09-22 | 新华三技术有限公司 | A kind of service message processing method and device |
| CN108108239A (en) * | 2017-12-29 | 2018-06-01 | 咪咕文化科技有限公司 | A kind of providing method of business function, device and computer readable storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9323588B2 (en) * | 2013-03-14 | 2016-04-26 | Comcast Cable Communications, Llc | Service platform architecture |
| US10885502B2 (en) * | 2016-09-28 | 2021-01-05 | Paypal, Inc. | Using disbursement signals at payment systems |
| US11074573B2 (en) * | 2017-10-27 | 2021-07-27 | International Business Machines Corporation | Processing mobile payments when disconnected from payment servers |
-
2019
- 2019-07-10 CN CN201910622082.6A patent/CN110442481B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101593387A (en) * | 2008-05-27 | 2009-12-02 | 中国移动通信集团公司 | A kind of method, system and equipment that uses local account to carry out remote payment |
| CN107153649A (en) * | 2016-03-02 | 2017-09-12 | 阿里巴巴集团控股有限公司 | A kind of data back up method and device |
| CN107038025A (en) * | 2016-09-28 | 2017-08-11 | 阿里巴巴集团控股有限公司 | System call method and device based on SOA framework |
| CN106648936A (en) * | 2016-12-29 | 2017-05-10 | Tcl集团股份有限公司 | Cooperative processing method and system based on microservices and server |
| CN106603708A (en) * | 2016-12-30 | 2017-04-26 | 中国建设银行股份有限公司 | Business processing method and device |
| CN107193663A (en) * | 2017-01-04 | 2017-09-22 | 新华三技术有限公司 | A kind of service message processing method and device |
| CN108108239A (en) * | 2017-12-29 | 2018-06-01 | 咪咕文化科技有限公司 | A kind of providing method of business function, device and computer readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| Poster: Benchmarking Microservice Systems for Software Engineering Research;Xiang Zhou等;《2018 IEEE/ACM 40th International Conference on Software Engineering: Companion (ICSE-Companion)》;20180830;全文 * |
| SOA在新一代支付系统中的应用设想;谈小生;《金融电子化》;20070907(第09期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110442481A (en) | 2019-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110442481B (en) | Service processing method, service component container and electronic equipment | |
| CN108876380B (en) | Transaction method and system based on centralized settlement and block chain deposit certificate | |
| CN109242453B (en) | Transaction method and system based on centralized settlement and block chain deposit certificate | |
| CN109377216B (en) | Transaction method and system based on centralized settlement and block chain deposit certificate | |
| CN110457142B (en) | Service processing method, system, machine room, architecture and electronic equipment | |
| CN108173706B (en) | Service marking method, device and equipment under multi-service system | |
| CN111382168B (en) | Node group creating method and node group-based transaction method in alliance chain network | |
| CN111756550A (en) | Block chain consensus method and device | |
| US8996714B2 (en) | State-dependent entity based implementation of a service oriented architected application | |
| CN109598407B (en) | Method and device for executing business process | |
| CN108647950B (en) | Transfer request processing method, device and equipment | |
| CN113205416A (en) | Service processing method and system based on block chain prediction machine | |
| CN105260292A (en) | Log recording method, apparatus and system | |
| CN110992040A (en) | Transaction processing method, device and equipment | |
| CN111651467A (en) | Block chain link point interface issuing and calling method and device | |
| CN110264332A (en) | The method, apparatus and electronic equipment that account is entered an item of expenditure in the accounts | |
| CN112433863A (en) | Micro-service calling method and device, terminal equipment and storage medium | |
| CN112288577A (en) | Transaction processing method and device for distributed service, electronic equipment and medium | |
| CN110782253B (en) | Transaction processing method, device and equipment based on block chain | |
| CN108596581B (en) | Verification method and device for resource transfer and electronic payment verification method and device | |
| CN111709748B (en) | Transaction execution method and device with business attribute and electronic equipment | |
| CN110852752B (en) | Method, device, equipment and storage medium for processing recharge order withdrawal exception | |
| CN108564433B (en) | Method, device and server for currency conversion | |
| CN106548331B (en) | Method and device for determining release sequence | |
| CN111651469B (en) | Method and device for managing blockchain system contracts |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201010 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201010 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |