Multi-platform order processing method and device, electronic equipment and storage medium

Through the multi-platform order processing method, order processing requests are distributed to the corresponding order pod, solving the problems of inefficient order processing and insufficient security in the prior art, and achieving isolation and efficient and secure processing of order data.

CN119474014APending Publication Date: 2025-02-18E-SURFING DIGITAL LIFE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411564295.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-05
Publication Date
2025-02-18

AI Technical Summary

Technical Problem

The existing order processing methods are inefficient, insufficient security, and lack of complete encryption and decryption solutions, resulting in the exposed order data and the inability to achieve data isolation.

Method used

The multi-platform order processing method is adopted to obtain the order processing requests from the upstream system, determine the target order ID and type, and distribute it to the corresponding order pod for processing, so as to achieve the isolation and secure processing of order data.

Benefits of technology

It improves the efficiency of order processing and data security, reduces the frequency of database query, realizes the isolation of order data, and avoids data exposure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119474014A_ABST
    Figure CN119474014A_ABST
Patent Text Reader

Abstract

The invention discloses a multi-platform order processing method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining an order processing request of an upstream system, determining a target order ID and a target order type according to the order processing request, and determining a target order Pod according to the target order type; distributing the target order ID to a target order Pod, enabling the target order Pod to obtain target order data according to the target order ID, and forwarding the target order data to a corresponding target order processing system; and performing order logic processing on the target order data through the target order processing system, and returning a processing result to the upstream system through the target order Pod. The order processing efficiency and the order data safety are improved, and the method can be widely applied to the technical field of data processing.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a multi-platform order processing method, device, electronic device and storage medium. Background Art

[0002] In the existing order processing method, all order data is stored in the database, and archiving orders does not work. The actual query is also upstream local query or query based on the business system, resulting in frequent database queries for each order processing; since the order status is updated frequently, it is not appropriate to use cache, and there is no complete encryption and decryption solution, resulting in order data being exposed and data isolation is not achieved; in addition, each pod will process multiple business data, resulting in confusion in query logs. In summary, the existing order processing method has the disadvantages of low efficiency and insufficient security. Summary of the invention

[0003] The purpose of the present invention is to solve one of the technical problems existing in the prior art to at least a certain extent.

[0004] To this end, an object of an embodiment of the present invention is to provide a multi-platform order processing method, which improves the efficiency of order processing and the security of order data.

[0005] Another object of an embodiment of the present invention is to provide a multi-platform order processing device.

[0006] In order to achieve the above technical objectives, the technical solutions adopted by the embodiments of the present invention include:

[0007] In one aspect, an embodiment of the present invention provides a multi-platform order processing method, comprising the following steps:

[0008] Obtain an order processing request from an upstream system, determine a target order ID and a target order type according to the order processing request, and determine a target order Pod according to the target order type;

[0009] Distribute the target order ID to the target order Pod, so that the target order Pod obtains the target order data according to the target order ID, and then forwards the target order data to the corresponding target order processing system;

[0010] The target order processing system performs order logic processing on the target order data, and returns the processing result to the upstream system through the target order Pod.

[0011] Further, in one embodiment of the present invention, determining the target order ID and the target order type according to the order processing request, and determining the target order Pod according to the target order type, specifically includes:

[0012] Parsing the order processing request to obtain the target order ID;

[0013] Determine a type key field according to the target order ID, and determine the target order type according to the type key field;

[0014] The target order processing system is determined according to the target order type, and the order Pod corresponding to the target order processing system is used as the target order Pod.

[0015] Further, in one embodiment of the present invention, distributing the target order ID to the target order Pod specifically includes:

[0016] When there are multiple target order Pods, the target IP address that needs to be requested for the target order ID is determined through a hash distribution algorithm;

[0017] The target order ID is distributed to the corresponding target order Pod according to the target IP address.

[0018] Further, in one embodiment of the present invention, the acquiring target order data according to the target order ID specifically includes:

[0019] Determine the type key field according to the target order ID, and traverse the Redis according to the type key field to obtain the corresponding order data to be processed;

[0020] Storing the pending order data in the local memory of the target order Pod;

[0021] The target order data is obtained by traversing the local memory according to the target order ID.

[0022] Further, in one embodiment of the present invention, returning the processing result to the upstream system through the target order Pod specifically includes:

[0023] When the target order data is processed successfully, the order status of the target order data is modified through the target order Pod, and the processing result is returned to the upstream system;

[0024] When the target order data processing fails, determining the cause of the failure according to the error code returned by the target order processing system;

[0025] When the failure reason is a business reason, the order status of the target order data is modified through the target order Pod, and the processing result is returned to the upstream system;

[0026] When the failure is caused by a network problem, the target order data is re-pushed to the target order processing system through the target order Pod for retry processing.

[0027] Further, in one embodiment of the present invention, the re-pushing of the target order data to the target order processing system for retry processing specifically includes:

[0028] Adding the target order data to a retry list, and re-pushing the target order data to the target order processing system according to the retry list;

[0029] When the retry succeeds, the target order data is deleted from the retry list, the order status of the target order data is modified through the target order Pod, and the retry result is returned to the upstream system;

[0030] When the number of retry failures reaches a preset number, a network abnormality prompt is returned to the upstream system through the target order Pod.

[0031] Furthermore, in one embodiment of the present invention, the multi-platform order processing method further includes the following steps:

[0032] Obtain an order archiving request from an upstream system, determine an archived order ID and an archived order type according to the order archiving request, and determine an archived order Pod according to the archived order type;

[0033] The archived order ID is distributed to the archived order Pod, so that the archived order Pod removes the archived order data according to the archived order ID, and notifies the corresponding order processing system to perform order archiving on the archived order data.

[0034] On the other hand, an embodiment of the present invention provides a multi-platform order processing device, including:

[0035] An order Pod determination module is used to obtain an order processing request from an upstream system, determine a target order ID and a target order type according to the order processing request, and determine a target order Pod according to the target order type;

[0036] An order data forwarding module, used for distributing the target order ID to the target order Pod, so that the target order Pod obtains the target order data according to the target order ID, and then forwards the target order data to the corresponding target order processing system;

[0037] The order data processing module is used to perform order logic processing on the target order data through the target order processing system, and return the processing result to the upstream system through the target order Pod.

[0038] On the other hand, an embodiment of the present invention provides an electronic device, comprising a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory, wherein the program, when executed by the processor, realizes the multi-platform order processing method as described above.

[0039] On the other hand, an embodiment of the present invention further provides a storage medium, which is a computer-readable storage medium used for computer-readable storage, and the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the multi-platform order processing method as described above.

[0040] The advantages and beneficial effects of the present invention will be partly given in the following description, partly become apparent from the following description, or be understood through the practice of the present invention:

[0041] The embodiment of the present invention obtains an order processing request from an upstream system, determines a target order ID and a target order type according to the order processing request, determines a target order Pod according to the target order type, distributes the target order ID to the target order Pod, so that the target order Pod obtains the target order data according to the target order ID, and then forwards the target order data to the corresponding target order processing system, performs order logic processing on the target order data through the target order processing system, and returns the processing result to the upstream system through the target order Pod. The embodiment of the present invention distributes the order ID of the order data requested for processing to different order Pods according to the order type, so that each order Pod only needs to cache and forward the order data of the same order type to the corresponding order processing system for order logic processing, without the need to frequently query the database, and achieves the isolation of order data, thereby improving the efficiency of order processing and the security of order data. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solution in the embodiments of the present invention, the following introduction is made to the drawings required for use in the embodiments of the present invention. It should be understood that the drawings introduced below are only for the convenience of clearly describing some embodiments of the technical solution of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0043] Figure 1 A step flow chart of a multi-platform order processing method provided by an embodiment of the present invention;

[0044] Figure 2A schematic diagram of the overall process of the multi-platform order processing method provided by an embodiment of the present invention;

[0045] Figure 3 A step flow chart of step S101 provided in an embodiment of the present invention;

[0046] Figure 4 A step flow chart of step S102 provided in an embodiment of the present invention;

[0047] Figure 5 Another step flow chart of step S102 provided in an embodiment of the present invention;

[0048] Figure 6 A step flow chart of step S103 provided in an embodiment of the present invention;

[0049] Figure 7 A step flow chart of step S1034 provided in an embodiment of the present invention;

[0050] Figure 8 Another step flow chart of the multi-platform order processing method provided by an embodiment of the present invention;

[0051] Fig. 9 A schematic diagram of the structure of a multi-platform order processing device provided by an embodiment of the present invention;

[0052] Fig.10 A schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention;

[0053] Fig.11 A schematic diagram of the structure of a storage medium provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0054] Embodiments of the present invention are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be understood as limitations on the present application. It should be noted that, although the functional module division is performed in the system schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order from the module division in the system schematic diagram or the flow chart. For the step numbers in the following embodiments, they are only set for the convenience of explanation, and the order between the steps is not limited in any way. The execution order of each step in the embodiment can be adaptively adjusted according to the understanding of those skilled in the art.

[0055] In the description of the present invention, the meaning of "a plurality" is two or more. If there is a description of the first or the second, it is only for the purpose of distinguishing the technical features, and it cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features. In addition, unless otherwise defined, all technical and scientific terms used in this document have the same meaning as those commonly understood by technicians in the technical field of this application. The terms used in this document are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0056] The multi-platform order processing method provided in the embodiment of the present invention can be applied to the terminal, can also be applied to the server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a set-top box, etc.; the server side can be configured as an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the multi-platform order processing method, etc., but is not limited to the above forms.

[0057] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0058] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with the relevant laws, regulations, and standards of the relevant countries and regions. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0059] The order processing request of the present invention is uniformly pushed by the upstream system, and the order type is identified through analysis, so as to be forwarded to the corresponding order processing system. The downstream order processing system receives the data in a pre-set format, and only needs to process the order data according to the configuration. However, the databases of multiple systems, such as middleware such as Redis and Kafka, are not interoperable, and data interaction requires network calls. Since the business order processing is cumbersome, the order cannot be quickly responded to the upstream system, so it needs to be designed as asynchronous processing, and the preliminary design is to quickly respond to the upstream, and then interact with the downstream orders one after another. In addition, since there are certain differences between the original order and the issued business order data, the unarchived orders in the middle need to be retained for a period of time. Archived orders do not need to be processed, and only unarchived orders need to be paid attention to.

[0060] There are two reasons why the present invention does not perform full persistent storage of business order data: first, the database resources of each system are not connected, and the database order data cannot be directly accessed, and the data already exists in each business system and does not need to be stored repeatedly, otherwise it is necessary to consider the accuracy of multiple data, data comparison and other work and storage resource issues; the present invention only needs to process unfinished orders, the data itself is incomplete, and once the order is archived, the data has no value, and the system that really needs persistent data is the downstream order processing business. Therefore, the present invention only needs to consider the verification of user interface permissions, order data permissions, request data decryption, identify order types for forwarding, and quickly respond to the upstream system order status and other work.

[0061] Although unfinished orders are persisted to Redis, in order to achieve data isolation and reduce the memory pressure of a single pod, the present invention can confirm that orders belong to different business scenarios according to rules and specify them to be pushed to different pods. In this way, a single pod only needs to cache the business it needs to process, thereby achieving the purpose of data isolation, non-interference, and non-memory occupation, and reducing the pressure of a single service.

[0062] like Figure 1FIG. 1 is a flow chart showing a method for processing multi-platform orders according to an embodiment of the present invention. Figure 1 The embodiment of the present invention provides a multi-platform order processing method, which specifically includes the following steps:

[0063] S101. Obtain an order processing request from an upstream system, determine a target order ID and a target order type according to the order processing request, and determine a target order Pod according to the target order type;

[0064] S102, distributing the target order ID to the target order Pod, so that the target order Pod obtains the target order data according to the target order ID, and then forwards the target order data to the corresponding target order processing system;

[0065] S103. Perform order logic processing on the target order data through the target order processing system, and return the processing result to the upstream system through the target order Pod.

[0066] Specifically, the embodiments of the present invention are mainly applied to a multi-order processing and distribution system across systems, especially in an enterprise-level environment where multiple types of orders (such as SaaS, PaaS, service orders, etc.) need to be processed efficiently, safely, and flexibly. Figure 2 The figure shows an overall flow chart of the multi-platform order processing method provided by an embodiment of the present invention, including an upstream system, an order processing and distribution cluster (composed of multiple order Pods) and a downstream order processing system. In this specific example, one pod is allocated to the downstream SaaS system order to store order data, two pods are allocated to the device PaaS order system to store order data, and each other's IP addresses are stored between the pods for synchronizing device data; two pods are allocated to the service order system to store order data, and each other's IP addresses are stored between the pods for synchronizing service order data.

[0067] The order distribution service is responsible for receiving HTTP requests from the upstream system and performing preliminary verification and decryption. In addition, the order type can be determined through preset rules to determine the pod corresponding to the request. Multiple pods use the hash diversion algorithm to calculate the IP address to be requested, which lays the foundation for data isolation and reducing memory consumption.

[0068] The order processing cluster consists of multiple Pods. In most scenarios, Pods only need to process one type of order. Pods of the same type of order synchronize data through communication. The Pod sends the order processing request to the downstream system and starts an asynchronous listening thread. After the downstream system completes the processing, the Pod receives the result and updates the order status, and returns the processing result to the front end.

[0069] The downstream order business system is responsible for specific order processing logic, such as inventory deductions, payment verification, service activation, etc.

[0070] The embodiment of the present invention distributes the order ID of the order data requested for processing to different order Pods according to the order type, so that each order Pod only needs to cache and forward the order data of the same order type to the corresponding order processing system for order logic processing, without the need to frequently query the database, and realizes the isolation of order data, thereby improving the efficiency of order processing and the security of order data.

[0071] like Figure 3 FIG. 1 is a flowchart of step S101 provided in an embodiment of the present invention, referring to FIG. Figure 3 As an optional implementation, a target order ID and a target order type are determined according to the order processing request, and a target order Pod is determined according to the target order type, which specifically includes:

[0072] S1011, parsing the order processing request to obtain the target order ID;

[0073] S1012. Determine a type key field according to the target order ID, and determine the target order type according to the type key field;

[0074] S1013. Determine a target order processing system according to the target order type, and use the order Pod corresponding to the target order processing system as the target order Pod.

[0075] Specifically, the embodiment of the present invention identifies the order type through a key field in the order ID. Therefore, the target order type can be determined by parsing the type key field of the target order ID, and the corresponding target order processing system can be determined according to the target order type, thereby determining the order Pod corresponding to the target order processing system as the target order Pod.

[0076] like Figure 4 FIG. 1 is a flow chart of step S102 provided in an embodiment of the present invention, referring to FIG. Figure 4 As an optional implementation, the target order ID is distributed to the target order Pod, which specifically includes:

[0077] S1021. When there are multiple target order Pods, the target IP address that needs to be requested for the target order ID is determined through a hash distribution algorithm;

[0078] S1022. Distribute the target order ID to the corresponding target order Pod according to the target IP address.

[0079] Specifically, when there are multiple order Pods corresponding to the target order processing system, there are also multiple determined target order Pods. At this time, the target IP address that needs to be requested by the target order ID is determined through the hash diversion algorithm, so that multiple target order IDs can be diverted to achieve load balancing of order data processing.

[0080] like Figure 5 FIG. 1 is another step flow chart of step S102 provided in an embodiment of the present invention, referring to FIG. Figure 5 As an optional implementation, obtaining target order data according to the target order ID specifically includes:

[0081] S1023. Determine the type key field according to the target order ID, and traverse the Redis according to the type key field to obtain the corresponding order data to be processed;

[0082] S1024. Storing the pending order data in the local memory of the target order Pod;

[0083] S1025. Obtain target order data by traversing the local memory according to the target order ID.

[0084] Specifically, when the target order Pod is started for the first time, the initial data is pulled from Redis, and the type key fields that can be processed are logically traversed. Once the corresponding order data is obtained, it is locked in Redis, and Redis no longer allows other order Pods to obtain the locked order data. The type key field is the basis for confirming which type of order data to process. The IP message containing the type key field is pushed to the order distribution service. The order distribution service then pulls the same type of order data to be processed through the type key field and stores it in the local memory. Subsequent operations are processed in memory, which can ensure that the data processed by each pod is isolated and no data of other types of business is stored. It should be noted that pods of the same type need to synchronize data to improve the robustness of the system; once the order status is modified or archived, the pod will synchronously update or delete the data stored in Redis to ensure data consistency.

[0085] like Figure 6 FIG. 1 is a flow chart of step S103 provided in an embodiment of the present invention, referring to FIG. Figure 6 As an optional implementation, the processing result is returned to the upstream system through the target order Pod, which specifically includes:

[0086] S1031. When the target order data is processed successfully, the order status of the target order data is modified through the target order Pod, and the processing result is returned to the upstream system;

[0087] S1032. When the target order data processing fails, the cause of the failure is determined according to the error code returned by the target order processing system;

[0088] S1033. When the failure is caused by business reasons, modify the order status of the target order data through the target order Pod, and return the processing result to the upstream system;

[0089] S1034. When the failure is caused by a network problem, the target order data is re-pushed to the target order processing system through the target order Pod for retry processing.

[0090] like Figure 7 FIG. 1 is another step flow chart of step S1034 provided in an embodiment of the present invention, referring to FIG. Figure 7 As an optional implementation, the target order data is pushed back to the target order processing system for retry processing, which specifically includes:

[0091] S10341. Add the target order data to the retry list, and push the target order data to the target order processing system again according to the retry list;

[0092] S10342. When the retry succeeds, the target order data is deleted from the retry list, the order status of the target order data is modified through the target order Pod, and the retry result is returned to the upstream system;

[0093] S10343. When the number of retry failures reaches the preset number, a network exception prompt is returned to the upstream system through the target order Pod.

[0094] Specifically, when the downstream returns an error code indicating a processing failure, the error code is used to determine whether the failure is caused by business reasons or network reasons. If it is caused by a network reason, the order data is stored from the order map to the retrying order (i.e., the retry list), and the data structure is a ConcurrentLinkedQueue. A strategy is formulated to implement three retries. If the network still fails, the upstream system is notified of the network anomaly, and the order is restored to its previous state. If the retry is successful, the retrying order data is removed and the retry result is returned.

[0095] In some optional embodiments, failover and automatic expansion mechanisms may be added to improve system robustness.

[0096] like Figure 8 FIG. 1 is another step flow chart of the multi-platform order processing method provided by an embodiment of the present invention, referring to FIG. Figure 8 As an optional implementation, the multi-platform order processing method further includes the following steps:

[0097] S201. Obtain an order archiving request from an upstream system, determine an archived order ID and an archived order type according to the order archiving request, and determine an archived order Pod according to the archived order type;

[0098] S202: Distribute the archived order ID to the archived order Pod, so that the archived order Pod removes the archived order data according to the archived order ID, and notifies the corresponding order processing system to archive the archived order data.

[0099] The above is a description of the method steps of the embodiment of the present invention. It can be recognized that the embodiment of the present invention distributes the order ID of the order data requested for processing to different order Pods according to the order type, so that each order Pod only needs to cache and forward the order data of the same order type to the corresponding order processing system for order logic processing, without the need to frequently query the database, and achieves the isolation of order data, thereby improving the efficiency of order processing and the security of order data.

[0100] Compared with the prior art, the embodiments of the present invention also have the following advantages:

[0101] 1) Use order rules and hash algorithms to distribute orders to different Pods for processing, achieve data isolation and service decoupling, improve system flexibility and scalability, reduce the coupling between systems, eliminate the need for the system to process irrelevant data, and reduce useless memory consumption.

[0102] 2) It uses an asynchronous method to interact with the downstream order business system and uses memory cache to increase data processing speed, which significantly improves the system's response speed to upstream requests, reduces the system's processing pressure, and improves the user experience.

[0103] 3) Memory management and data synchronization of single pod orders: Use local memory to cache order data, and define only the orders that the pod needs to process through Redis locks and policies. If there are multiple pods of the same type, the data is synchronized and saved in another data object through the IP addresses between pods. This data only needs to be accessed when other pods crash, which reduces the efficiency of order retrieval, query and update, and avoids scenarios where data query processing is not required.

[0104] 4) Using the memory method reduces the number of database accesses and improves the efficiency of data processing. At the same time, the consistency and integrity of the data are guaranteed through the data synchronization mechanism.

[0105] like Fig. 9 FIG. 1 is a schematic diagram of the structure of a multi-platform order processing device provided by an embodiment of the present invention, referring to FIG. Fig. 9 , an embodiment of the present invention provides a multi-platform order processing device, comprising:

[0106] The order Pod determination module is used to obtain the order processing request from the upstream system, determine the target order ID and target order type according to the order processing request, and determine the target order Pod according to the target order type;

[0107] The order data forwarding module is used to distribute the target order ID to the target order Pod, so that the target order Pod obtains the target order data according to the target order ID, and then forwards the target order data to the corresponding target order processing system;

[0108] The order data processing module is used to perform order logic processing on the target order data through the target order processing system, and return the processing results to the upstream system through the target order Pod.

[0109] The contents of the above method embodiments are all applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0110] The embodiment of the present invention further provides an electronic device, the electronic device comprising: a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory, and the program is executed by the processor to realize the above-mentioned multi-platform order processing method. The electronic device can be any intelligent terminal including a tablet computer, a vehicle-mounted computer, etc.

[0111] like Fig.10 FIG. 1 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention, referring to FIG. Fig.10 , an embodiment of the present invention provides an electronic device, including:

[0112] The processor 1001 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present invention.

[0113] The memory 1002 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 1002, and the processor 1001 calls and executes the multi-platform order processing method of the embodiment of the present invention;

[0114] Input / output interface 1003, used to implement information input and output;

[0115] The communication interface 1004 is used to realize the communication interaction between the device and other devices. The communication can be realized through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0116] A bus 1005 , which transmits information between various components of the device (e.g., the processor 1001 , the memory 1002 , the input / output interface 1003 , and the communication interface 1004 );

[0117] The processor 1001 , the memory 1002 , the input / output interface 1003 and the communication interface 1004 are connected to each other in communication within the device via the bus 1005 .

[0118] like Fig.11 FIG. 1 is a schematic diagram of a storage medium according to an embodiment of the present invention. Fig.11 The embodiment of the present invention further provides a storage medium, which is a computer-readable storage medium used for computer-readable storage. The storage medium stores one or more programs 1101, and the one or more programs 1101 can be executed by one or more processors to implement the above-mentioned multi-platform order processing method.

[0119] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0120] The embodiment of the present invention also discloses a computer program product or a computer program, wherein the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes Figure 1 The method shown.

[0121] In some selectable embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the above-mentioned boxes can sometimes be executed in reverse order. In addition, the embodiment presented and described in the flow chart of the present invention is provided by way of example, for the purpose of providing a more comprehensive understanding of technology. The disclosed method is not limited to the operation and logic flow presented herein. Selectable embodiments are expected, wherein the order of various operations is changed and the sub-operation of a part for which is described as a larger operation is performed independently.

[0122] In addition, although the present invention is described in the context of functional modules, it should be understood that, unless otherwise specified to the contrary, one or more of the above-mentioned functions and / or features can be integrated into a single physical device and / or software module, or one or more functions and / or features can be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the present invention. More specifically, in view of the properties, functions and internal relationships of the various functional modules in the device disclosed herein, the actual implementation of the module will be understood within the conventional skills of the engineer. Therefore, those skilled in the art can implement the present invention set forth in the claims without excessive experimentation using ordinary techniques. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0123] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the above methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0124] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in conjunction with such instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in conjunction with such instruction execution systems, devices or apparatuses.

[0125] More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be a paper or other suitable medium on which the above-mentioned program is printed, since the above-mentioned program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or processing in other suitable ways as necessary, and then stored in a computer memory.

[0126] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0127] In the above description of this specification, the description with reference to the terms "one embodiment / example", "another embodiment / example" or "certain embodiments / examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0128] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

[0129] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above embodiments. Those skilled in the art may make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of this application.

Claims

1. A multi-platform order processing method, characterized in that: The following steps are involved: Obtain an order processing request from an upstream system, determine a target order ID and a target order type according to the order processing request, and determine a target order Pod according to the target order type; Distribute the target order ID to the target order Pod, so that the target order Pod obtains the target order data according to the target order ID, and then forwards the target order data to the corresponding target order processing system; The target order processing system performs order logic processing on the target order data, and returns the processing result to the upstream system through the target order Pod.

2. A multi-platform order processing method according to claim 1, characterized in that: Determining the target order ID and the target order type according to the order processing request, and determining the target order Pod according to the target order type, specifically includes: Parsing the order processing request to obtain the target order ID; Determine a type key field according to the target order ID, and determine the target order type according to the type key field; The target order processing system is determined according to the target order type, and the order Pod corresponding to the target order processing system is used as the target order Pod.

3. A multi-platform order processing method according to claim 1, characterized in that: The step of distributing the target order ID to the target order Pod specifically includes: When there are multiple target order Pods, the target IP address that needs to be requested for the target order ID is determined through a hash distribution algorithm; The target order ID is distributed to the corresponding target order Pod according to the target IP address.

4. A multi-platform order processing method according to claim 1, characterized in that: The step of obtaining target order data according to the target order ID specifically includes: Determine the type key field according to the target order ID, and traverse the Redis according to the type key field to obtain the corresponding order data to be processed; Storing the pending order data in the local memory of the target order Pod; The target order data is obtained by traversing the local memory according to the target order ID.

5. A multi-platform order processing method according to claim 1, characterized in that: The returning the processing result to the upstream system through the target order Pod specifically includes: When the target order data is processed successfully, the order status of the target order data is modified through the target order Pod, and the processing result is returned to the upstream system; When the target order data processing fails, determining the cause of the failure according to the error code returned by the target order processing system; When the failure reason is a business reason, the order status of the target order data is modified through the target order Pod, and the processing result is returned to the upstream system; When the failure is caused by a network problem, the target order data is re-pushed to the target order processing system through the target order Pod for retry processing.

6. A multi-platform order processing method according to claim 5, characterized in that: The re-pushing of the target order data to the target order processing system for retry processing specifically includes: Adding the target order data to a retry list, and re-pushing the target order data to the target order processing system according to the retry list; When the retry succeeds, the target order data is deleted from the retry list, the order status of the target order data is modified through the target order Pod, and the retry result is returned to the upstream system; When the number of retry failures reaches a preset number, a network abnormality prompt is returned to the upstream system through the target order Pod.

7. A multi-platform order processing method according to any one of claims 1 to 6, characterized in that: The multi-platform order processing method further comprises the following steps: Obtain an order archiving request from an upstream system, determine an archived order ID and an archived order type according to the order archiving request, and determine an archived order Pod according to the archived order type; The archived order ID is distributed to the archived order Pod, so that the archived order Pod removes the archived order data according to the archived order ID, and notifies the corresponding order processing system to perform order archiving on the archived order data.

8. A multi-platform order processing device, characterized in that: include: An order Pod determination module is used to obtain an order processing request from an upstream system, determine a target order ID and a target order type according to the order processing request, and determine a target order Pod according to the target order type; An order data forwarding module, used for distributing the target order ID to the target order Pod, so that the target order Pod obtains the target order data according to the target order ID, and then forwards the target order data to the corresponding target order processing system; The order data processing module is used to perform order logic processing on the target order data through the target order processing system, and return the processing result to the upstream system through the target order Pod.

9. An electronic device, characterized in that: The electronic device includes a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the steps of the multi-platform order processing method as described in any one of claims 1 to 7 are realized.

10. A storage medium, the storage medium being a computer-readable storage medium, used for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the multi-platform order processing method as described in any one of claims 1 to 7.