Methods, devices, equipment, systems, and media for acquiring messages across public clouds

Abstract

This application discloses a method, apparatus, device, system, and medium for cross-public cloud message acquisition. The method includes: monitoring a cloud object storage space; upon detecting a message acquisition trigger signal file in the cloud object storage space, creating a message acquisition task, wherein the message acquisition trigger signal file indicates that the cloud object storage space has received a business message sent by a first application system located in a first public cloud; executing the message acquisition task to acquire the business message corresponding to the message acquisition trigger signal file in the cloud object storage space; generating a business message based on the business message corresponding to the message acquisition trigger signal file; and providing the business message to a second application system located in a second public cloud, wherein the first public cloud is different from the second public cloud. According to the embodiments of this application, cross-public cloud transmission of business messages can be achieved.

Description

Technical Field

[0001] This application belongs to the field of data processing, and in particular relates to a method, apparatus, device, system and medium for obtaining messages across public clouds. Background Technology

[0002] With the rapid development of cloud services, more and more application systems can be deployed through the cloud. Clouds can be categorized as public clouds, private clouds, hybrid clouds, etc. One or more application systems can reside on the same public cloud. Different application systems may reside on the same public cloud or on different public clouds. In the actual execution of business operations, different application systems residing on different public clouds need to interact and obtain messages provided by each other. However, to ensure public cloud security, different public clouds do not establish network protocol relationships; that is, different public clouds cannot directly exchange messages. Therefore, a method for obtaining messages across public clouds is urgently needed. Summary of the Invention

[0003] This application provides a method, apparatus, device, system, and medium for obtaining messages across public clouds, which enables the transmission of business messages across public clouds.

[0004] In a first aspect, embodiments of this application provide a method for obtaining messages across public clouds, comprising: monitoring a cloud object storage space; upon detecting a message obtaining trigger signal file in the cloud object storage space, creating a message obtaining task, wherein the message obtaining trigger signal file is used to indicate that the cloud object storage space has received a business message sent by a first application system, the first application system being located in a first public cloud; executing the message obtaining task to obtain the business message corresponding to the message obtaining trigger signal file in the cloud object storage space; generating a business message based on the business message corresponding to the message obtaining trigger signal file; and providing the business message to a second application system, the second application system being located in a second public cloud, the first public cloud being different from the second public cloud.

[0005] Secondly, embodiments of this application provide a cross-public cloud message acquisition device, comprising: a monitoring module for monitoring a cloud object storage space; a task creation module for creating a message acquisition task when a message acquisition trigger signal file is detected in the cloud object storage space, wherein the message acquisition trigger signal file indicates that the cloud object storage space has received a business message sent by a first application system, the first application system being located in a first public cloud; a task execution module for executing the message acquisition task and acquiring the business message corresponding to the message acquisition trigger signal file in the cloud object storage space; a message generation module for generating a business message based on the business message corresponding to the message acquisition trigger signal file; and a message providing module for providing the business message to a second application system, the second application system being located in a second public cloud, the first public cloud being different from the second public cloud.

[0006] Thirdly, embodiments of this application provide a cross-public cloud message acquisition device, including: a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the cross-public cloud message acquisition method of the first aspect.

[0007] Fourthly, embodiments of this application provide a cross-public cloud message acquisition system, including: a message capture device for executing the cross-public cloud message acquisition method of the first aspect; a cloud object storage space; a first application system located in a first public cloud; and a second application system located in a second public cloud, wherein the first public cloud and the second public cloud are different.

[0008] Fifthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the cross-public cloud message acquisition method of the first aspect.

[0009] Fifthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the cross-public cloud message acquisition method of the first aspect.

[0010] This application provides a method, apparatus, device, system, and medium for cross-public cloud message acquisition. By monitoring the cloud object storage space, it determines in real-time whether a first application system located in a first public cloud has sent a business message to the cloud object storage space based on whether a message acquisition trigger signal file appears in the cloud object storage space. If it is determined that the cloud object storage space has a message acquisition trigger signal file, meaning the first application system in the first public cloud has sent the business message to the cloud object storage space, a message acquisition task is created, executed, and the business message is retrieved from the cloud object storage space. This message is then processed into a business message subscribed to by a second application system located in a second public cloud, enabling the second application system to obtain the business message and achieving cross-public cloud transmission of business messages. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a schematic diagram illustrating an example application scenario of the cross-public cloud message acquisition method provided in the embodiments of this application;

[0013] Figure 2 A flowchart illustrating a method for obtaining messages across public clouds according to an embodiment of this application;

[0014] Figure 3 A schematic diagram illustrating an example of cloud object storage space that a public cloud can use, as provided in the embodiments of this application.

[0015] Figure 4 A schematic diagram illustrating another example of cloud object storage space that can be used by a public cloud as provided in the embodiments of this application;

[0016] Figure 5 A flowchart illustrating a method for obtaining messages across public clouds, provided as another embodiment of this application;

[0017] Figure 6 A schematic diagram illustrating an example of the processing logic within the message capturing device provided in an embodiment of this application;

[0018] Figure 7 A schematic diagram of the structure of a cross-public cloud message acquisition device provided in an embodiment of this application;

[0019] Figure 8 This is a schematic diagram of the structure of a cross-public cloud message acquisition device provided in an embodiment of this application. Detailed Implementation

[0020] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0021] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0022] With the rapid development of cloud services, more and more application systems can be deployed through the cloud. Clouds can be categorized as public clouds, private clouds, hybrid clouds, etc. One or more application systems can reside on the same public cloud. Different application systems may reside on the same public cloud or on different public clouds. During actual business operations, different application systems residing on different public clouds need to obtain messages provided by each other to interact. However, to ensure public cloud security, different public clouds do not establish network protocol relationships; that is, different public clouds cannot directly exchange messages.

[0023] The cross-public cloud message acquisition method, apparatus, device, system, medium, and computer program products provided in this application can be applied to scenarios involving cross-public cloud transmission of service messages. For ease of explanation, an example is given here to illustrate the application scenario. Figure 1 This is a schematic diagram illustrating an example application scenario of the cross-public cloud message acquisition method provided in the embodiments of this application. For example... Figure 1As shown, a first application system 111 is configured on the first public cloud 11, and a second application system 121 is configured on the second public cloud 12. The first application system 111 can be used to execute application service A1, and the second application system 121 can be used to execute application service B1. Application service B1 requires data from the business messages provided by application service A1 to perform its functions. The first public cloud 11 and the second public cloud 12 are different; that is, the first public cloud 11 and the second public cloud 12 are two independent public clouds, and no network protocol relationship has been established between them. Any public cloud where an application system providing business messages is located can be referred to as the first public cloud 11, and any public cloud where an application system that needs to obtain data from business messages is located can be referred to as the second public cloud 12. The first application system 111 can send business messages to the cloud object storage space 13 and store them in the cloud object storage space 13. In this embodiment of the application, the method for obtaining messages across public clouds can be executed by the message capture device 14. The message capture device 14 can monitor the cloud object storage space 13 to determine in real time whether the first application system 111 located on the first public cloud 11 sends business messages to the cloud object storage space 13. If it is determined that the cloud object storage space 13 has business messages, a message acquisition task is created, the message acquisition task is executed, the business message is acquired from the cloud object storage space 13, and processed into a message subscribed to by the second application system 121 located on the second public cloud 121. The second application system 121 can acquire the subscribed message from the message capture device 14, realizing the transmission of business messages across public clouds, and the real-time performance of acquiring business messages across public clouds is also very good.

[0024] The following sections will introduce the methods, devices, equipment, systems, media, and computer program products for obtaining messages across public clouds.

[0025] The first aspect of this application provides a method for obtaining messages across public clouds. This method can be executed by a message obtaining device or equipment that is not limited thereto. For example, the message obtaining device that is across public clouds can be implemented as the message capturing device 14 mentioned above. Figure 2 A flowchart illustrating a method for obtaining messages across public clouds according to an embodiment of this application. Figure 2 As shown, the method for obtaining messages across public clouds may include steps S201 to S205.

[0026] In step S201, the cloud object storage space is monitored.

[0027] Cloud object storage is a storage space independent of the first and second public clouds, and can store data such as business messages sent from the public clouds. In some examples, cloud object storage may include Cloud Object Storage (COS) buckets.

[0028] A first application system on the first public cloud sends a service message to the cloud object storage space, which then stores the service message. In some examples, when the cloud object storage space receives a service message, it can generate a message acquisition trigger signal file corresponding to that service message. In other examples, the first application system sends a service message to the cloud object storage space simultaneously with the service message, and also sends the corresponding message acquisition trigger signal file to the cloud object storage space. This message acquisition trigger signal file is used to indicate that the cloud object storage space has received the service message sent by the first application system.

[0029] The monitoring of the cloud object storage space can be real-time, so as to promptly determine that the first application system has provided business messages to the cloud object storage space, thereby improving the real-time performance of this cross-public cloud message acquisition method.

[0030] In some examples, the cloud object storage space includes cloud object storage buckets, but the number of cloud object storage buckets in the cloud object storage space is not limited here. It can monitor the cloud object storage buckets specified by the first application system and the second application system. The first application system can pre-agree with the second application system on the cloud object storage buckets to be used in the cloud object storage space. The message capturing device can pre-determine the cloud object storage buckets that the first application system can agree to use with the second application system, so as to monitor the specified cloud object storage buckets, further improving the accuracy and real-time performance of the monitoring.

[0031] For example, Figure 3 This is a schematic diagram of an example of cloud object storage space that can be used by a public cloud as provided in the embodiments of this application. Figure 3 The cloud object storage space shown includes cloud object storage buckets 1 to 3. The first application system 111 located on the first public cloud 11 and the second application system 121 located on the second public cloud 12 are designated to use cloud object storage bucket 3. When the second application system 121 needs to obtain data from the business message of the first application system 121, the business message sent by the first application system 121, the message acquisition trigger signal file, etc. are stored in the cloud object storage bucket 3. The message capture device 14 can monitor the cloud object storage bucket 3.

[0032] In some examples, the cloud object storage space includes cloud object storage buckets, and the number of cloud object storage buckets in the cloud object storage space is not limited here. It can monitor specified paths within the cloud object storage buckets specified by the first application system and the second application system. The first application system can pre-agree with the second application system on the specified paths of the cloud object storage buckets used in the cloud object storage space. The message capturing device can pre-determine the specified paths within the cloud object storage buckets that the first application system and the second application system can agree upon, in order to monitor the specified paths within the specified cloud object storage buckets, further improving the accuracy and real-time performance of the monitoring.

[0033] For example, Figure 4 This is a schematic diagram of another example of cloud object storage space that can be used by the public cloud provided in the embodiments of this application. Figure 4 The cloud object storage space shown includes cloud object storage bucket 1 and cloud object storage bucket 2. Cloud object storage bucket 2 includes storage paths event1\ and event2\. The first application system 111 located on the first public cloud 11 and the second application system 121 located on the second public cloud 12 specify to use the specified path event1\ in cloud object storage bucket 2. When the second application system 121 needs to obtain data from the business message of the first application system 121, the business message sent by the first application system 121, the message acquisition trigger signal file, etc. are stored in the specified path event1\ in cloud object storage bucket 2. The message capture device 14 can monitor the specified path event1\ in cloud object storage bucket 2.

[0034] In step S202, if a message retrieval trigger signal file is detected in the cloud object storage space, a message retrieval task is created.

[0035] The appearance of a message retrieval trigger signal file in the cloud object storage space indicates that the first application system has sent a business message. In response to the detection of this trigger signal file in the cloud object storage space, a message retrieval task can be created. The message retrieval task is a task used to instruct the execution of message retrieval steps.

[0036] In step S203, a message acquisition task is executed to retrieve the business message corresponding to the message acquisition trigger signal file from the cloud object storage space.

[0037] This message retrieval task retrieves the business message corresponding to the message retrieval trigger signal file from the cloud object storage space. There is a correspondence between the message retrieval trigger signal file and the business message; the corresponding business message can be determined based on the message retrieval trigger signal file. In some examples, at least a portion of the filename of the message retrieval trigger signal file may be the same as at least a portion of the filename of the business message; the business message corresponding to the message retrieval trigger signal file can be determined through the filename.

[0038] In step S204, a service message is generated based on the service message corresponding to the message acquisition trigger signal file.

[0039] It can parse business messages to obtain the data in the business messages, and generate business messages subscribed to by the second application system based on the data in the business messages.

[0040] In step S205, the business message is provided to the second application system.

[0041] The second application system can obtain the business messages it needs to execute the corresponding business.

[0042] For details regarding the first application system, the first public cloud, the second application system, and the second public cloud, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0043] In this embodiment, by monitoring the cloud object storage space and determining in real time whether the first application system located in the first public cloud has sent business messages to the cloud object storage space based on whether a message acquisition trigger signal file appears in the cloud object storage space, the system can effectively detect such messages. If it is determined that the cloud object storage space has a message acquisition trigger signal file, indicating that the first application system in the first public cloud has sent business messages to the cloud object storage space, a message acquisition task is created and executed. This task retrieves the business message from the cloud object storage space and processes it into a business message subscribed to by the second application system located in the second public cloud, enabling the second application system to access the business message and achieving cross-public cloud transmission of business messages. Because the cloud object storage space is monitored in real time, business messages sent by the first application system located in the first public cloud can be detected promptly, improving the real-time performance, stability, and accuracy of cross-public cloud transmission of business messages. This is particularly beneficial for services with high real-time requirements, such as transactions, ensuring that transaction messages are acquired by the second message system in the first instance.

[0044] Furthermore, the cross-public cloud message acquisition method provided in this application embodiment is executed independently of the first application system and the second application system. It separates the technical logic of message acquisition, parsing, and transmission from the business logic of the first application system (upstream) and the second application system (downstream), thus decoupling the technical logic from the business logic. This simplifies the development of the downstream system, allowing it to focus more on business processing functions and shortening the processing chain. Due to this decoupling, the cross-public cloud message acquisition method provided in this application embodiment can support business scenarios across different application systems, exhibiting excellent adaptability and versatility for different application systems and business scenarios.

[0045] Figure 5 A flowchart of a method for obtaining messages across public clouds provided in another embodiment of this application. Figure 5 and Figure 2 The difference is that, Figure 5 The cross-public cloud message acquisition method shown may further include steps S206 to S212. Figure 2 Step S204 can be further refined as follows: Figure 5 Step S2041 in the middle, Figure 2 Step S205 can be further refined as follows: Figure 5 Step S2051 in the process.

[0046] In step S206, the message acquisition task is stored in the memory storage database.

[0047] An in-memory database is a database stored in memory. The data in an in-memory database is stored in memory. There is no limitation on the type of in-memory database. For example, an in-memory database can be implemented as a remote dictionary service (Redis).

[0048] In step S207, the message acquisition task is persisted from the memory storage database to the disk storage database.

[0049] To ensure the secure execution of the message retrieval task and guarantee data security, the task needs to be persisted from the in-memory storage database to a disk storage database; that is, the message retrieval task needs to be persisted. The type of disk storage database is not limited here; for example, it could be implemented as an Oracle database. The specific persistence method is also not limited here; for example, AOF (Append Only File) can be used to persist the message retrieval task.

[0050] In step S208, if the business message corresponding to the message acquisition trigger signal file is successfully retrieved from the cloud object storage space, an acquisition success signal file is generated.

[0051] Upon successful retrieval of a business message, a retrieval success signal file is generated. This file indicates that the business message corresponding to the message retrieval trigger signal file was successfully retrieved from the cloud object storage space. In some examples, a copy of the generated retrieval success signal file may also be stored in the cloud object storage space.

[0052] In step S2041, when a successful acquisition signal file is detected, a service message is generated based on the service message corresponding to the message acquisition trigger signal file.

[0053] A successful acquisition signal file is detected, indicating that the business message corresponding to the message acquisition trigger signal file has been successfully retrieved from the cloud object storage space, and a business message is generated based on the business message.

[0054] In step S209, if it fails to retrieve the business message corresponding to the message retrieval trigger signal file in the cloud object storage space, a retrieval failure signal file is generated.

[0055] In the event of a failure to retrieve a business message, a retrieval failure signal file is generated. This file indicates a failure to retrieve the business message corresponding to the message retrieval trigger signal file from the cloud object storage space. In some examples, a copy of the generated retrieval failure signal file may also be stored in the cloud object storage space.

[0056] In step S210, the signal file is scanned periodically. When a failed acquisition signal file is detected, the service message corresponding to the message acquisition trigger signal file is retrieved again from the cloud object storage space until the service message is successfully acquired, or the number of failed acquisitions of the service message reaches the failure count threshold.

[0057] The system can periodically scan the generated signal files. The timing interval can be set according to the scenario, requirements, experience, etc., and is not limited here. In some examples, when a failed acquisition signal file is detected, it can be determined that the acquisition of the business message has failed. The business message needs to be acquired again, and the above process is repeated until the business message is successfully acquired, generating a successful acquisition signal file. In some examples, when a failed acquisition signal file is detected, it can be determined that the acquisition of the business message has failed. The business message needs to be acquired again, and the above process is repeated until the number of failed acquisitions reaches a failure threshold. The failure threshold is the boundary value of the number of failures that will trigger an alarm. If the number of failed acquisitions of the business message reaches the failure threshold, a fault or other abnormal situation may occur, and an alarm needs to be issued.

[0058] In step S211, an alarm message is issued when the number of service message failures reaches the failure count threshold.

[0059] If the number of failed service messages reaches a certain threshold, an anomaly may occur. An alarm message can be sent to notify relevant personnel promptly, facilitating timely resolution of the anomaly. The type of alarm message is not limited; it can include email, SMS, audio, or video signals. The sending path for the alarm message can be pre-defined to send it to the appropriate recipient; for example, the alarm message can be sent to the equipment of the service maintenance provider.

[0060] By generating success and failure signal files, it is possible to ensure that no business message is lost, thus ensuring that the corresponding business is not missed. When a business message fails to be acquired, it can be detected and processed in a timely manner, reducing the packet loss rate.

[0061] In step S2051, the business message is pushed to the message queue so that the second application system can retrieve the business message from the message queue.

[0062] The generated business messages can be pushed to a message queue for storage. The second application system has access to the message queue, allowing it to retrieve subscribed business messages. The message queue enables point-to-point message publishing and subscription. In some examples, the message queue can be RabbitMQ, which is based on the Advanced Message Queuing Protocol (AMQP), offering high reliability and security, and meeting the requirements for data consistency, stability, and reliability.

[0063] In step S212, in response to the second application system retrieving a business message from the message queue, a processing tag is added to the business message.

[0064] The processing flag indicates that the business message has been retrieved by the second application system. The processing flag serves as a response identifier for the second application system when it retrieves the business message from the message queue. By adding the processing flag, the business message can be prevented from being retrieved repeatedly, thus achieving a closed loop in the business process.

[0065] For ease of understanding, the internal processing logic of the message capture device that executes this cross-public cloud message acquisition method is explained here. Figure 6 This is a schematic diagram illustrating an example of the processing logic within the message capturing device provided in an embodiment of this application. Figure 6As shown, the message capturing device 300 may include an event listener 301, a central controller 302, a task manager 303, a memory storage database 304, a disk storage database 305, an event capturer 306, a message manager 307, a message queue 308, and an exception task timer poller 309. The interactions between the event listener 301, central controller 302, task manager 303, memory storage database 304, disk storage database 305, event capturer 306, message manager 307, message queue 308, and exception task timer poller 309 are shown in a1 to a13 below:

[0066] a1. Event listener 301 monitors the object storage space in the cloud in real time;

[0067] a2. Event listener 301 listens to the message, obtains the trigger signal file, and notifies the central controller 302.

[0068] a3. The central controller 302 controls the task manager 303 to create message acquisition tasks;

[0069] a4. Task Manager 303 persists the message acquisition task from memory storage database 304 to disk storage database 305;

[0070] a5. Task Manager 303 notifies Central Controller 302 that the message acquisition task has been completed;

[0071] a6. The intermediate controller 302 assigns a message acquisition task to the event capturer 306;

[0072] a7. Event catcher 306 executes message retrieval tasks to retrieve business messages from the cloud object storage space;

[0073] a8. Event catcher 306 generates a success signal file or a failure signal file based on whether the acquisition of the service message is successful or unsuccessful, and feeds the success signal file or the failure signal file back to the central controller 302.

[0074] a9. The central controller 302 receives the successful acquisition signal file and notifies the message manager 307.

[0075] a10. Message manager 307 generates business messages based on business messages and pushes the business messages to message queue 308.

[0076] a11. The abnormal task timer poller 309 periodically initiates a scan of the central controller 302;

[0077] a12. If the abnormal task timer poller 309 detects a failed acquisition signal file, it sends a request to the central controller 302 to request to retrieve the business message from the cloud object storage space again.

[0078] a13. The central controller 302 controls the event capture 306 to retrieve business messages from the cloud object storage space again.

[0079] The specific contents of a1 to a13 mentioned above can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0080] In some embodiments, the interaction of business messages between the first application system and the second application system can also be completed through a private cloud that has network connectivity with both the first and second public clouds. A reverse proxy server can be deployed in the private cloud to act as a bridge, forwarding business messages between the first and second application systems. That is, business messages sent by the first application system can be forwarded to the second application system through a reverse proxy server located in the private cloud, which is connected to both the first and second public clouds. In some examples, the reverse proxy server may be an Nginx server, but it is not limited to this.

[0081] The second aspect of this application provides a message acquisition device across public clouds. Figure 7 This is a schematic diagram of the structure of a cross-public cloud message acquisition device provided in an embodiment of this application. For example... Figure 7 As shown, the cross-public cloud message acquisition device 400 may include a listening module 401, a task creation module 402, a task execution module 403, a message generation module 404, and a message providing module 405.

[0082] The listening module 401 can be used to monitor the object storage space in the cloud.

[0083] The task creation module 402 can be used to create a message retrieval task when a message retrieval trigger signal file is detected in the cloud object storage space.

[0084] The message acquisition trigger signal file is used to indicate that the cloud object storage space has received a business message sent by the first application system. The first application system is located in the first public cloud.

[0085] The task execution module 403 can be used to execute message acquisition tasks and retrieve business messages corresponding to the message acquisition trigger signal file in the cloud object storage space.

[0086] The message generation module 404 can be used to generate business messages based on the business messages corresponding to the message acquisition trigger signal file.

[0087] The message providing module 405 can be used to provide business messages to a second application system.

[0088] The second application system is located in the second public cloud, which is different from the first public cloud.

[0089] In this embodiment, by monitoring the cloud object storage space and determining in real time whether the first application system located in the first public cloud has sent business messages to the cloud object storage space based on whether a message acquisition trigger signal file appears in the cloud object storage space, the system can effectively detect such messages. If it is determined that the cloud object storage space has a message acquisition trigger signal file, indicating that the first application system in the first public cloud has sent business messages to the cloud object storage space, a message acquisition task is created and executed. This task retrieves the business message from the cloud object storage space and processes it into a business message subscribed to by the second application system located in the second public cloud, enabling the second application system to access the business message and achieving cross-public cloud transmission of business messages. Because the cloud object storage space is monitored in real time, business messages sent by the first application system located in the first public cloud can be detected promptly, improving the real-time performance, stability, and accuracy of cross-public cloud transmission of business messages. This is particularly beneficial for services with high real-time requirements, such as transactions, ensuring that transaction messages are acquired by the second message system in the first instance.

[0090] Furthermore, the cross-public cloud message acquisition method provided in this application embodiment is executed independently of the first application system and the second application system. It separates the technical logic of message acquisition, parsing, and transmission from the business logic of the first application system (upstream) and the second application system (downstream), thus decoupling the technical logic from the business logic. This simplifies the development of the downstream system, allowing it to focus more on business processing functions and shortening the processing chain. Due to this decoupling, the cross-public cloud message acquisition method provided in this application embodiment can support business scenarios across different application systems, exhibiting excellent adaptability and versatility for different application systems and business scenarios.

[0091] In some embodiments, the task creation module 402 can also be used to: store the message acquisition task in a memory storage database; and persist the message acquisition task from the memory storage database to a disk storage database.

[0092] In some embodiments, the task execution module 403 can also be used to generate a successful acquisition signal file when the business message corresponding to the message acquisition trigger signal file is successfully acquired in the cloud object storage space.

[0093] The message generation module 404 can be specifically used to generate a business message based on the business message corresponding to the message acquisition trigger signal file when a successful acquisition signal file is detected.

[0094] In some embodiments, the above-described cross-public cloud message acquisition device 400 may further include a scanning module and an alarm module.

[0095] The task execution module 403 can also be used to generate an acquisition failure signal file in the event that the acquisition of the business message corresponding to the message acquisition trigger signal file fails to be obtained in the cloud object storage space.

[0096] The scanning module can be used to scan signal files at regular intervals, and when a failed acquisition signal file is detected, it notifies the task execution module 403, so that the task execution module 403 can re-acquire the business message corresponding to the message acquisition trigger signal file in the cloud object storage space until the business message is successfully acquired, or the number of failed acquisitions of the business message reaches the failure count threshold.

[0097] The alarm module can be used to issue alarm information when the number of failed business messages reaches the failure count threshold.

[0098] In some embodiments, the message providing module 405 may be specifically used to push business messages to a message queue so that the second application system can obtain business messages from the message queue.

[0099] The second application system has permission to access the message queue.

[0100] In some embodiments, the above-described cross-public cloud message acquisition device 400 may further include a tagging module.

[0101] The tagging module can be used to add processing tags to business messages in response to a second application system retrieving business messages from a message queue.

[0102] The processing tag indicates that the business message has been acquired by the second application system.

[0103] In some embodiments, cloud object storage space includes cloud object storage buckets.

[0104] The listening module 401 can be specifically used to: listen to the cloud object storage buckets specified by the first application system and the second application system; or, listen to the specified paths in the cloud object storage buckets specified by the first application system and the second application system.

[0105] In some embodiments, the above-described message acquisition device 400 across public clouds may include a private cloud control module.

[0106] The private cloud control module can be used to forward business messages sent by the first application system to the second application system through a reverse proxy server located in the private cloud.

[0107] The private cloud is connected to the first public cloud and the second public cloud networks respectively.

[0108] A third aspect of this application also provides a message acquisition device for cross-public cloud environments. Figure 8 This is a schematic diagram of the structure of a cross-public cloud message acquisition device provided in one embodiment of this application. For example... Figure 8 As shown, the cross-public cloud message acquisition device 500 includes a memory 501, a processor 502, and a computer program stored on the memory 501 and capable of running on the processor 502.

[0109] In some examples, the processor 502 described above may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits that may be configured to implement the embodiments of this application.

[0110] Memory 501 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the packet acquisition method across a public cloud according to embodiments of this application.

[0111] The processor 502 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 501, in order to implement the cross-public cloud message acquisition method in the above embodiments.

[0112] In some examples, the cross-public cloud message acquisition device 500 may also include a communication interface 503 and a bus 504. For example, Figure 8 As shown, the memory 501, processor 502, and communication interface 503 are connected through bus 504 and complete communication with each other.

[0113] The communication interface 503 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application. Input devices and / or output devices can also be connected through the communication interface 503.

[0114] Bus 504 includes hardware, software, or both, that couples components of message acquisition device 500 across a public cloud together. For example, and not limitingly, bus 504 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 504 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0115] The fourth aspect of this application provides a message acquisition system across public clouds, which may include a message capture device, a cloud object storage space, a first application system, and a second application system.

[0116] The message capture device can execute the cross-public cloud message acquisition method in the above embodiments, which can be found in the relevant descriptions in the above embodiments and will not be repeated here.

[0117] The first application system is located on the first public cloud, and the second application system is located on the second public cloud. The first public cloud and the second public cloud are different and have not opened network protocol connections with each other.

[0118] For details on the cross-public cloud message acquisition system, please refer to the relevant descriptions in the above embodiments, which can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0119] A fifth aspect of this application provides a computer-readable storage medium storing computer program instructions. When executed by a processor, these instructions can implement the cross-public cloud message acquisition method described in the above embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.

[0120] The sixth aspect of this application provides a computer program product in which the instructions are executed by the processor of an electronic device, causing the electronic device to perform the cross-public cloud message acquisition method in the above embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0121] It should be clarified that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For the device embodiments, equipment embodiments, system embodiments, computer-readable storage medium embodiments, and computer program product embodiments, the relevant parts can be referred to the description section of the method embodiments. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application. Furthermore, for the sake of brevity, detailed descriptions of known method techniques are omitted here.

[0122] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0123] Those skilled in the art will understand that the above embodiments are exemplary and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, specification, and claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to identify names and not to indicate any particular order. No reference numerals in the claims should be construed as limiting the scope of protection. The functionality of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A method for obtaining messages across public clouds, characterized in that, The method is applied to a message capturing device, which includes an event listener, a central controller, a task manager, an event capturer, a message manager, a message queue, and an exception task timer poller; the method includes: The event listener is used to monitor the cloud object storage space, which is a storage space independent of the first public cloud and the second public cloud. When a message acquisition trigger signal file is detected in the cloud object storage space, the central controller controls the task manager to create a message acquisition task. The message acquisition trigger signal file is used to indicate that the cloud object storage space has received a business message sent by a first application system, which is located in a first public cloud. The event catcher is used to perform a message acquisition task to retrieve the business message corresponding to the message acquisition trigger signal file from the cloud object storage space. The event catcher generates a success signal file or a failure signal file based on whether the acquisition of the service message is successful or unsuccessful, and feeds the success signal file or the failure signal file back to the central controller. When the central controller receives the successful acquisition signal file, it uses the message manager to generate a service message subscribed to by the second application system based on the data in the service message corresponding to the message acquisition trigger signal file. The message manager is used to push the business message to the message queue; The business message in the message queue is provided to the second application system so that the second application system can execute the business corresponding to the business message. The second application system is located in the second public cloud and has the right to access the message queue. The first public cloud is different from the second public cloud. The abnormal task timer poller periodically scans the central controller. If the abnormal task timer poller detects a failure signal file, the central controller controls the event catcher to retrieve the service message from the cloud object storage space again until the service message is successfully retrieved, and the success signal file is generated, or the number of times the service message is retrieved fails reaches the failure count threshold. The cloud object storage space includes cloud object storage buckets, and the cloud object storage space being monitored includes: Monitor the cloud object storage buckets specified by the first application system and the second application system; or, Listen to the specified path in the cloud object storage bucket specified by the first application system and the second application system.

2. The method according to claim 1, characterized in that, After the creation of the message acquisition task, the following is included: The message acquisition task is stored in an in-memory storage database; The message acquisition task is persisted from the memory storage database to the disk storage database.

3. The method according to claim 1, characterized in that, Also includes: An alarm message is issued when the number of failed service messages reaches the failure count threshold.

4. The method according to claim 1, characterized in that, Also includes: In response to the second application system retrieving the business message from the message queue, a processing flag is added to the business message, the processing flag indicating that the business message has been retrieved by the second application system.

5. The method according to claim 1, characterized in that, Also includes: The business messages sent by the first application system are forwarded to the second application system through a reverse proxy server located in a private cloud. The private cloud is connected to the networks of the first public cloud and the second public cloud respectively.

6. A message acquisition device across public clouds, characterized in that, This is applied to a message capturing device, which includes an event listener, a central controller, a task manager, an event capturer, a message manager, a message queue, and an exception task timer poller; the device includes: The listening module is used to listen to the cloud object storage space using the event listener, wherein the cloud object storage space is a storage space independent of the first public cloud and the second public cloud. The task creation module is used to control the task manager to create a message acquisition task when a message acquisition trigger signal file is detected in the cloud object storage space. The message acquisition trigger signal file is used to indicate that the cloud object storage space has received a business message sent by a first application system, which is located in a first public cloud. The task execution module is used to execute a message acquisition task using the event catcher, and to acquire the business message corresponding to the message acquisition trigger signal file in the cloud object storage space; and to generate an acquisition success signal file or an acquisition failure signal file based on whether the acquisition of the business message is successful or unsuccessful using the event catcher; the message generation module is used to generate a business message subscribed to by the second application system based on the data in the business message corresponding to the message acquisition trigger signal file when the central controller receives the acquisition success signal file; A message providing module is used to push the business message to the message queue using the message manager; and to provide the business message in the message queue to a second application system so that the second application system can execute the business corresponding to the business message. The second application system is located in a second public cloud and has the right to access the message queue. The first public cloud is different from the second public cloud. The scanning module is used to periodically scan the central controller using the abnormal task timer poller. If the abnormal task timer poller detects a failure signal file, it notifies the task execution module, which then uses the central controller to control the event catcher to retrieve the service message from the cloud object storage space again until the service message is successfully retrieved, generating the success signal file, or until the number of failures to retrieve the service message reaches a failure count threshold. The cloud object storage space includes cloud object storage buckets; The monitoring module is also used to monitor the cloud object storage buckets specified by the first application system and the second application system; and to monitor the specified paths in the cloud object storage buckets specified by the first application system and the second application system. After generating a success signal file or a failure signal file, the success signal file or the failure signal file is fed back to the central controller.

7. A message acquisition device for cross-public cloud environments, characterized in that, include: Processor and memory storing computer program instructions; When the processor executes the computer program instructions, it implements the cross-public cloud message acquisition method as described in any one of claims 1 to 5.

8. A message acquisition system across public clouds, characterized in that, include: A message capture device for performing the cross-public cloud message acquisition method as described in any one of claims 1 to 5; Cloud object storage space; The first application system is located on the first public cloud; The second application system is located on a second public cloud, which is different from the first public cloud.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the cross-public cloud message acquisition method as described in any one of claims 1 to 5.

10. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the cross-public cloud message acquisition method as described in any one of claims 1 to 5.

Images