A method, apparatus, equipment and medium for updating e-commerce data

Abstract

This specification discloses an e-commerce data update method, apparatus, device, and medium, comprising: obtaining a data change message pushed by a specified e-commerce platform in a pre-set local marketplace; determining the data message type corresponding to the data change message and the e-commerce type corresponding to the specified e-commerce platform; determining a message queue for storing the data change message based on the data message type corresponding to the data change message; determining a corresponding processing plugin based on the e-commerce type corresponding to the specified e-commerce platform; processing the data change message in the message queue of the data change message according to the processing plugin to obtain a processed data change result; and updating the e-commerce data accordingly based on the processed data change result.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for updating e-commerce data. Background Technology

[0002] As enterprises expand their procurement scale and their procurement system management becomes more standardized, it becomes increasingly difficult for them to invest a large number of procurement personnel in managing general office supplies and low-value consumables. They generally adopt the method of building their own e-commerce system to list existing suppliers or contracted e-commerce products on the e-commerce system in order to achieve fast ordering and simplify supplier management.

[0003] Because different e-commerce platforms are heterogeneous systems with differences between them, there are many difficulties in building local e-commerce platforms in terms of software services. Summary of the Invention

[0004] This specification provides one or more embodiments of a method, apparatus, device, and medium for updating e-commerce data, which is used to solve the technical problems mentioned in the background art.

[0005] One or more embodiments of this specification employ the following technical solutions:

[0006] This specification provides one or more embodiments of a method for updating e-commerce data, including:

[0007] In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform.

[0008] Determine the message queue for storing the data change message based on the data message type corresponding to the data change message;

[0009] Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin;

[0010] In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result;

[0011] Based on the processed data change results, the corresponding e-commerce data is updated.

[0012] Furthermore, before processing the data change message according to the processing plugin, the method further includes:

[0013] Get the number of unprocessed data changes in the message queue;

[0014] The number of processing plugins in the message queue is determined based on the number of unprocessed data changes.

[0015] Furthermore, before obtaining the data change message pushed by the specified e-commerce platform, the method further includes:

[0016] A pre-configured API interface layer provides a calling interface for the designated e-commerce platform, which is used to receive the data change message sent by the designated e-commerce platform.

[0017] Furthermore, before obtaining the data change message pushed by the specified e-commerce platform, the method further includes:

[0018] The parameter information of the designated e-commerce platform is obtained through a pre-set operational monitoring node;

[0019] Establish a connection with the designated e-commerce platform based on the parameter information of the designated e-commerce platform.

[0020] Furthermore, if the designated e-commerce platform does not have a compatible processing plugin, the method further includes:

[0021] Based on the specified e-commerce type, perform extended registration to obtain the corresponding extended processing plugin.

[0022] Furthermore, the data change messages include price change messages, inventory change messages, promotion change messages, and transportation change messages.

[0023] Furthermore, the method is applied to an e-commerce data update system, which includes a local marketplace node, multiple external e-commerce nodes, and an operation monitoring sub-node; when the data change message is a price change message, the method further includes:

[0024] In the local e-commerce node, the running supervision sub-node obtains the price change message pushed by the designated external e-commerce node, determines the message type corresponding to the price change message and the e-commerce type corresponding to the designated external e-commerce node, determines the message queue for storing the price change message based on the message type corresponding to the price change message, and determines the corresponding first processing plugin in the message queue of the price change message based on the e-commerce type corresponding to the designated external e-commerce node.

[0025] The local e-commerce node processes the price change message according to the first processing plugin to obtain the processed price change result, and updates the corresponding e-commerce data according to the processed price change result.

[0026] This specification provides one or more embodiments of an e-commerce data updating device, the device comprising:

[0027] The type determination unit obtains a data change message pushed by a specified e-commerce platform in a pre-set local e-commerce platform, and determines the data message type corresponding to the data change message and the e-commerce type corresponding to the specified e-commerce platform.

[0028] The queue determination unit determines the message queue for storing the data change message based on the data message type corresponding to the data change message.

[0029] The plugin determination unit determines the corresponding processing plugin based on the e-commerce type corresponding to the specified e-commerce platform.

[0030] The processing unit processes the data change message in the message queue according to the processing plugin to obtain the processed data change result;

[0031] The update unit updates the e-commerce data accordingly based on the processed data change results.

[0032] This specification provides one or more embodiments of an e-commerce data updating device, comprising:

[0033] At least one processor; and,

[0034] A memory communicatively connected to the at least one processor; wherein,

[0035] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0036] In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform.

[0037] Determine the message queue for storing the data change message based on the data message type corresponding to the data change message;

[0038] Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin;

[0039] In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result;

[0040] Based on the processed data change results, the corresponding e-commerce data is updated.

[0041] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0042] In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform.

[0043] Determine the message queue for storing the data change message based on the data message type corresponding to the data change message;

[0044] Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin;

[0045] In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result;

[0046] Based on the processed data change results, the corresponding e-commerce data is updated.

[0047] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0048] This specification's embodiments decouple the acquisition and processing logic of data change messages from various e-commerce platforms using message queues. Furthermore, this specification's embodiments significantly reduce system development workload and ensure compatibility with different e-commerce types when integrating with multiple mature e-commerce platforms. Additionally, since the system in this specification's embodiments is an independent, stand-alone microservice, it does not affect the business logic of the local e-commerce platform. Attached Figure Description

[0049] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0050] Figure 1 A flowchart illustrating a method for updating e-commerce data provided in one or more embodiments of this specification;

[0051] Figure 2 A schematic diagram of the structure of an e-commerce message integration device provided in one or more embodiments of this specification;

[0052] Figure 3 A schematic diagram of the data processing provided for one or more embodiments of this specification;

[0053] Figure 4 A schematic diagram of the structure of an e-commerce data updating device provided in one or more embodiments of this specification;

[0054] Figure 5 This is a schematic diagram of the structure of an e-commerce data updating device provided in one or more embodiments of this specification. Detailed Implementation

[0055] This specification provides an embodiment of a method, apparatus, device, and medium for updating e-commerce data.

[0056] As corporate procurement scales expand and procurement systems become increasingly standardized, companies often find it difficult to dedicate a large number of procurement personnel to managing general office supplies and low-value consumables. They typically adopt a self-built local online store model, listing products from existing suppliers or contracted e-commerce platforms to facilitate rapid ordering and simplify supplier management. Against this backdrop, integrating self-built local systems with mature e-commerce platforms is a current trend in corporate online store development. However, for software service providers, developing and building such an integrated online store system across multiple e-commerce platforms is an extremely complex undertaking.

[0057] Because different e-commerce platforms are heterogeneous systems, their calling methods, standard interfaces, and parameters differ. When building a local e-commerce platform, software services need to integrate with multiple e-commerce platforms one by one. This not only results in a large workload and long development cycle but also creates highly complex and chaotic system integration relationships. Against this backdrop, a complete and scalable e-commerce integration device has become an important research direction for software service providers.

[0058] In the context described above, this specification's embodiments employ a message queue to decouple the e-commerce interface from the local e-commerce system, connecting them in a loosely coupled manner. For different e-commerce platforms, message integration plugins can be extended to process e-commerce messages according to certain rules before sending them to the message queue. A built-in e-commerce message processing module performs business logic transformation on the e-commerce messages, ultimately providing them to the self-built e-commerce platform through a unified standard service interface layer. Furthermore, the message processing program can be elastically scaled based on the data volume of e-commerce messages and the backlog of the message queue, ensuring the timeliness of business data processing.

[0059] In addition, the embodiments in this specification also provide a visual monitoring module for operation and maintenance personnel. This module is responsible for managing the global parameter settings of the e-commerce message integration device, plugin version management, load balancing settings of the message processing program, etc. Simultaneously, it provides monitoring functionality for the overall operating status of the device, enabling operation and maintenance personnel to quickly view the system status. For example, the monitoring console can view the status of connected e-commerce platforms, the number of interface calls, the call throughput, the message types in the message queue, and the message backlog level in the queue. This solves the problems of complex system integration relationships, long development cycles, and difficulty in monitoring and management when integrating multiple different e-commerce platforms into a shopping mall system.

[0060] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0061] Figure 1 This diagram illustrates a process for updating e-commerce data according to one or more embodiments of this specification. This process can be executed by an e-commerce data updating system. For different e-commerce platforms, this system can update the data on the local platform after an external e-commerce platform issues a data change message, greatly facilitating enterprise procurement. Certain input parameters or intermediate results in the process can be manually adjusted to help improve accuracy.

[0062] The method flow steps of the embodiments in this specification are as follows:

[0063] S102, in a pre-set local marketplace, obtain a data change message pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform.

[0064] In the embodiments described in this specification, the local marketplace can be a self-operated marketplace used by the enterprise for procurement. This marketplace can connect to multiple e-commerce platforms to facilitate the enterprise's purchase of goods. The designated e-commerce platform can be any one of the multiple e-commerce platforms. Data change messages can include price change messages, inventory change messages, promotion change messages, shipping change messages, etc. For example, if the price of item 'a' on e-commerce platform A is adjusted, e-commerce platform A needs to send a message about the price adjustment of item 'a' to the local marketplace; this message is a data change message.

[0065] It should be noted that the message types can include the price change messages, inventory change messages, promotion change messages, and shipping change messages mentioned above. The e-commerce type can be an identifier for the e-commerce platform, such as e-commerce platform A or e-commerce platform B.

[0066] In the embodiments of this specification, before obtaining the data change message pushed by the designated e-commerce platform, a calling interface can be provided to the designated e-commerce platform through a pre-set API interface layer. The calling interface is used to receive the data change message sent by the designated e-commerce platform.

[0067] It's worth noting that the API interface layer provides a unified, stable, and standardized calling interface that shields the technical interface and parameter differences between different e-commerce platforms. This ensures the stability of the local e-commerce platform's functionality when switching or adding backend e-commerce platforms.

[0068] Furthermore, in this embodiment of the specification, before obtaining the data change message pushed by the designated e-commerce platform, the parameter information of the designated e-commerce platform can be obtained through a pre-set operation monitoring node; and a connection can be established with the designated e-commerce platform based on the parameter information of the designated e-commerce platform.

[0069] S104, determine the message queue for storing the data change message based on the data message type corresponding to the data change message.

[0070] In the embodiments of this specification, the aforementioned data change messages are stored in corresponding message queues. By utilizing different channels of the message queues, messages of different content types are stored in their respective message queues, thereby improving the processing efficiency of data change messages.

[0071] S106, determine the corresponding processing plugin based on the e-commerce type corresponding to the specified e-commerce platform.

[0072] In the embodiments of this specification, the processing plugin can set different message processing logic according to different e-commerce platforms. That is, after determining the identifier corresponding to a specified e-commerce platform, the processing plugin corresponding to that e-commerce platform can be determined.

[0073] In the embodiments of this specification, if the designated e-commerce platform does not have a compatible processing plugin, it can be extended for development. When the extension begins, it can be registered according to the e-commerce type of the designated e-commerce platform to obtain the corresponding extended processing plugin.

[0074] S108, in the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result.

[0075] In the embodiments of this specification, when the processing plugin processes the data change message, it may be based on existing processing methods, which will not be described in detail in the embodiments of this specification.

[0076] In the embodiments of this specification, before processing the data change message according to the processing plugin, the number of unprocessed data changes in the message queue can be obtained first; then, based on the number of unprocessed data changes, the number of processing plugins in the message queue can be determined.

[0077] It should be noted that, in implementing cluster operation, the embodiments in this specification obtain unprocessed data changes in the manner described above, which can make full use of the server processing capabilities within the cluster, process messages as quickly and stably as possible, and achieve message backlog-free processing.

[0078] S110, update the e-commerce data accordingly based on the processed data change results.

[0079] Furthermore, the embodiments of this specification can be applied to an e-commerce data update system, the system including a local e-commerce node, multiple external e-commerce nodes, and an operation monitoring sub-node; when the data change message is a price change message, the embodiments of this specification can be implemented through the following scheme:

[0080] In the local e-commerce node, the operation and supervision sub-node obtains a price change message pushed by a designated external e-commerce node, determines the message type corresponding to the price change message and the e-commerce type corresponding to the designated external e-commerce node, determines the message queue for storing the price change message based on the message type corresponding to the price change message, and determines the corresponding first processing plugin in the message queue of the price change message based on the e-commerce type corresponding to the designated external e-commerce node; the local e-commerce node processes the price change message according to the first processing plugin to obtain the processed price change result, and updates the corresponding e-commerce data based on the processed price change result.

[0081] It should be noted that, in conjunction with the aforementioned technical features, this specification discloses a general method for updating e-commerce data. This method decouples the acquisition and processing logic of data change messages from various e-commerce platforms through a message queue. Furthermore, this specification embodiment can utilize a load balancer to improve the concurrency capability of message processing. This specification embodiment also adds a standard API interface layer, encapsulating the interfaces of multiple different e-commerce platforms, ensuring consistency in their external interface declarations and calling methods, and achieving message integration across multiple e-commerce platforms with different architectures. This solves prominent problems in multiple implementation projects, such as long development cycles for integrating different e-commerce platforms, diverse e-commerce integration interface specifications, and low e-commerce data processing efficiency.

[0082] The embodiments described in this specification significantly reduce system development workload and ensure compatibility with different e-commerce types when integrating multiple mature e-commerce platforms. Furthermore, since the system in these embodiments is an independent, self-running microservice, it does not affect the business logic of the local e-commerce platform. In addition, these embodiments demonstrate good application effects for upgrading legacy systems and integrating and expanding e-commerce services into new systems.

[0083] Furthermore, the embodiments of this specification also provide a general e-commerce message integration device, which aims to solve the problems of inconsistent e-commerce interfaces and calling methods in multiple implementation projects, complex integration relationships among multiple e-commerce platforms with long development cycles, and difficulty in monitoring the integration process.

[0084] The e-commerce message integration device in the embodiments of this specification may include two parts: a server and a client. The relevant modules of the server include:

[0085] 1) Message Handler. This separates message retrieval from message processing using a message queue. This part can be divided into three modules:

[0086] A) E-commerce message subscription module. This module connects to different e-commerce platforms based on their technical parameters and retrieves data change messages pushed out by them. The messages are then processed and normalized according to certain rules.

[0087] B) Data storage in message queues. After e-commerce messages are acquired and processed through the above steps, they are stored in message queues. By utilizing different channels of the message queues, messages of different content types are stored in their respective queues, increasing the processing efficiency of consumers and providing a basis for the on-demand scaling of the consumer processing program.

[0088] C) Message Processing Plugin. This plugin is the consumer of the message queue. Different message processing logic can be developed for different e-commerce platforms. In other words, multiple message processing plugins can be developed for different e-commerce types, and selected according to integration requirements. Even better, this plugin can dynamically scale the message processing program based on the backlog of messages in the queue. That is, the processing program data can be set according to the backlog level to achieve cluster operation. This fully utilizes the processing capacity of the servers within the cluster, processing messages as quickly and stably as possible, achieving zero message backlog.

[0089] 2) API Interface Layer: This module shields the technical interfaces and parameter differences between different e-commerce platforms, providing a unified, stable, and standardized calling interface to the outside world. This ensures that when backend e-commerce platforms are switched or added, the frontend functionality remains relatively stable, reducing system modifications and updates.

[0090] 3) System Operation Monitoring Module: This module is responsible for managing the global parameter settings of the e-commerce message integration device, plugin version management, load balancing settings of the message processing program, etc. It also provides monitoring functionality for the overall device's operational status, enabling maintenance personnel to quickly view the system status. For example, the monitoring console can view the e-commerce integration status, the number of API calls, call throughput, message content types in the queue, and message backlog levels in the queue.

[0091] The client application is primarily designed to support the rapid integration of this device into self-built e-commerce systems. By referencing this client, self-built e-commerce systems can quickly connect to the integrated device of this invention without needing to concern themselves with complex remote call parameters in the backend.

[0092] It should be noted that the key points of the embodiments in this specification are as follows:

[0093] 1. The e-commerce message processing plugin in the e-commerce message integration device is selectively used based on the type of e-commerce. If no suitable plugin type is available, extended development is possible; the system can register extended plugins.

[0094] 2. The API interface layer masks the interface differences between multiple heterogeneous systems, ensuring a stable interface and calling method. Future expansion into new e-commerce types will also maintain this API interface layer unchanged, thus minimizing the need for major code adjustments to the e-commerce business system.

[0095] 3. The local e-commerce system utilizes an e-commerce integration device, which separates e-commerce-related processing logic from the local e-commerce platform's own business logic. This minimizes the impact of the integrated e-commerce functionality on the local e-commerce platform's core business. Generally, e-commerce messages are frequent and their processing logic is complex, consuming significant hardware resources. If this processing is mixed with the e-commerce platform's core functionality, it will not only put considerable pressure on the server but also affect the performance of complex logical operations such as search engines and intelligent matching. In other words, when e-commerce messages are numerous and processing logic is complex, the substantial consumption of performance resources will significantly impact the functionality and performance of the self-built e-commerce business system.

[0096] 4. Monitoring Console for the E-commerce Integration Device. This console serves as the core external interaction channel for the e-commerce integration device, displaying the operating status of the system host cluster, such as the consumption of system CPU, memory, and I / O resources; the status of system business message processing, such as the total number of messages pushed by e-commerce, the number of messages processed, message processing speed, and the current backlog level of different types of messages. It also allows administrators to view business message processing logs and historical records. Even better, it provides the function of dynamically scaling and expanding the message processing program, ensuring that there is virtually no message backlog or that the backlog is within an acceptable range.

[0097] Furthermore, Figure 2 This diagram illustrates the structure of an e-commerce message integration device provided in one or more embodiments of this specification. The device includes an e-commerce message subscription module, an e-commerce message processing module, a message queue data storage module, and an API unified interface module. It also includes a monitoring console capable of monitoring and viewing the operating status and message processing details.

[0098] Furthermore, Figure 3 This is a schematic diagram illustrating the data processing flow provided for one or more embodiments of this specification. The following example illustrates the integration of a local e-commerce platform with D-e-commerce.

[0099] First, the project manager negotiated with Business D and signed a framework agreement, which stipulated the categories and prices of the products to be subscribed to, as well as the types of messages to be subscribed from the e-commerce platform.

[0100] During system initialization or whenever data changes occur, the e-commerce platform pushes messages. The message subscription and notification module can quickly capture these notifications and send them to multiple queues according to their type. Simultaneously, the e-commerce message processing module, acting as a consumer of these message queues, receives callback notifications. Based on the stored e-commerce type and message type, the system can choose to activate different message processing plugins.

[0101] Then, the message processing plugin stores the constructed data source into the local e-commerce system through the auxiliary client of the e-commerce message processing module, thereby completing the entire message consumption and processing process.

[0102] Figure 4 This is a schematic diagram of the structure of an e-commerce data updating device provided in one or more embodiments of this specification. The device includes: a type determination unit 402, a queue determination unit 404, a plug-in determination unit 406, a processing unit 408, and an updating unit 410.

[0103] The type determination unit 402 obtains a data change message pushed by a specified e-commerce platform in a pre-set local e-commerce platform, and determines the data message type corresponding to the data change message and the e-commerce type corresponding to the specified e-commerce platform.

[0104] The queue determination unit 404 determines the message queue for storing the data change message based on the data message type corresponding to the data change message;

[0105] The plugin determination unit 406 determines the corresponding processing plugin based on the e-commerce type corresponding to the specified e-commerce platform.

[0106] Processing unit 408 processes the data change message in the message queue of the data change message according to the processing plugin to obtain the processed data change result;

[0107] The update unit 410 updates the e-commerce data accordingly based on the processed data change results.

[0108] Figure 5 A schematic diagram of the structure of an e-commerce data updating device provided for one or more embodiments of this specification includes:

[0109] At least one processor; and,

[0110] A memory communicatively connected to the at least one processor; wherein,

[0111] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0112] In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform.

[0113] Determine the message queue for storing the data change message based on the data message type corresponding to the data change message;

[0114] Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin;

[0115] In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result;

[0116] Based on the processed data change results, the corresponding e-commerce data is updated.

[0117] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0118] In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform.

[0119] Determine the message queue for storing the data change message based on the data message type corresponding to the data change message;

[0120] Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin;

[0121] In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result;

[0122] Based on the processed data change results, the corresponding e-commerce data is updated.

[0123] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0124] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0125] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for updating e-commerce data, characterized in that, The method includes: In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform. Determine the message queue for storing the data change message based on the data message type corresponding to the data change message; Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin; In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result; Based on the processed data change results, update the corresponding e-commerce data; Before processing the data change message according to the processing plugin, the method further includes: Get the number of unprocessed data changes in the message queue; The number of processing plugins in the message queue is determined based on the number of unprocessed data changes.

2. The method according to claim 1, characterized in that, Before obtaining the data change message pushed by the specified e-commerce platform, the method further includes: A pre-configured API interface layer provides a calling interface for the designated e-commerce platform, which is used to receive the data change message sent by the designated e-commerce platform.

3. The method according to claim 1, characterized in that, Before obtaining the data change message pushed by the specified e-commerce platform, the method further includes: The parameter information of the designated e-commerce platform is obtained through a pre-set operational monitoring node; Establish a connection with the designated e-commerce platform based on the parameter information of the designated e-commerce platform.

4. The method according to claim 1, characterized in that, If the specified e-commerce platform does not have a compatible processing plugin, the method further includes: Based on the specified e-commerce type, perform extended registration to obtain the corresponding extended processing plugin.

5. The method according to claim 1, characterized in that, The data change messages include price change messages, inventory change messages, promotion change messages, and shipping change messages.

6. The method according to claim 1, characterized in that, The method is applied to an e-commerce data update system, which includes a local e-commerce node, multiple external e-commerce nodes, and an operation monitoring sub-node. When the data change message is a price change message, the method further includes: In the local e-commerce node, the running supervision sub-node obtains the price change message pushed by the designated external e-commerce node, determines the message type corresponding to the price change message and the e-commerce type corresponding to the designated external e-commerce node, determines the message queue for storing the price change message based on the message type corresponding to the price change message, and determines the corresponding first processing plugin in the message queue of the price change message based on the e-commerce type corresponding to the designated external e-commerce node. The local e-commerce node processes the price change message according to the first processing plugin to obtain the processed price change result, and updates the corresponding e-commerce data according to the processed price change result.

7. An e-commerce data updating device, characterized in that, The device comprises: The type determination unit obtains a data change message pushed by a specified e-commerce platform in a pre-set local e-commerce platform, and determines the data message type corresponding to the data change message and the e-commerce type corresponding to the specified e-commerce platform. The queue determination unit determines the message queue for storing the data change message based on the data message type corresponding to the data change message. The plugin determination unit determines the corresponding processing plugin based on the e-commerce type corresponding to the specified e-commerce platform. The processing unit processes the data change message in the message queue according to the processing plugin to obtain the processed data change result; The update unit updates the e-commerce data accordingly based on the processed data change results. Before processing the data change message according to the processing plugin, the process further includes: Get the number of unprocessed data changes in the message queue; The number of processing plugins in the message queue is determined based on the number of unprocessed data changes.

8. A device for updating e-commerce data, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform. Determine the message queue for storing the data change message based on the data message type corresponding to the data change message; Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin; In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result; Based on the processed data change results, update the corresponding e-commerce data; Before processing the data change message according to the processing plugin, the process further includes: Get the number of unprocessed data changes in the message queue; The number of processing plugins in the message queue is determined based on the number of unprocessed data changes.

9. A non-volatile computer storage medium, characterized in that, The computer-executable instructions are stored thereon and are configured as follows: In a pre-defined local marketplace, obtain data change messages pushed by a designated e-commerce platform, and determine the data message type corresponding to the data change message and the e-commerce type corresponding to the designated e-commerce platform. Determine the message queue for storing the data change message based on the data message type corresponding to the data change message; Based on the e-commerce type corresponding to the specified e-commerce platform, determine the corresponding processing plugin; In the message queue of the data change message, the data change message is processed according to the processing plugin to obtain the processed data change result; Based on the processed data change results, update the corresponding e-commerce data; Before processing the data change message according to the processing plugin, the process further includes: Get the number of unprocessed data changes in the message queue; The number of processing plugins in the message queue is determined based on the number of unprocessed data changes.

Images