Intelligent asynchronous data exchange across microservices in a distributed environment

Abstract

In an example embodiment, a specialized architecture is utilized in conjunction with a message broker to enable asynchronous communications. The specialized architecture provides central components within each data center to enable the communication, and also is able to segregate functionality across different microservice landscapes. A message broker alone may not be sharable across data centers for various technical reasons, such as security concerns, latency, or other technical constraints. Topic names may be utilized by the message broker to ensure delivery of the message to the correct microservice in the other data center.

What is claimed is: 
     
       1. A system comprising:
 at least one hardware processor; and 
 a computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising:
 monitoring, at a distributor microservice in a first data center, one or more topics of a first message broker, the one or more topics having titles indicative of messages intended to be received by a data center other than the first data center; and 
 upon detection at the distributor microservice of a message posted at the first message broker by a first sender microservice to a first topic of the one or more topics:
 identifying, based on information in the message, a destination data center and a destination landscape; 
 retrieving a destination name and destination location from a landscape configuration file accessed by the distributor microservice, using the destination data center and destination landscape; and 
 sending the message from the distributor microservice to a router microservice of the destination data center, using the retrieved destination name and destination location, the router microservice configured to post the message to a second topic in a message broker of the destination data center. 
 
 
 
     
     
       2. The system of  claim 1 , wherein the destination landscape is derived from the landscape configuration file using the destination data center and a sender landscape identified in a name of the first topic. 
     
     
       3. The system of  claim 1 , wherein the titles indicative of messages intended to be received by a data center other than the first data center include a predefined piece of text in the titles. 
     
     
       4. The system of  claim 1 , wherein the message further includes a use case, and wherein the operations further comprise:
 retrieving a use case location from the landscape configuration file using the use case location; and 
 wherein the router microservice is further configured to determine a receiver use case location using a second landscape configuration file accessed by the router microservice and wherein the second topic includes the receiver use case location in its name. 
 
     
     
       5. The system of  claim 1 , wherein the first message broker further receives an additional message posted to a topic having a title indicative of messages intended to be received by the first data center and, in response to receiving the additional message, sends the additional message within the first data center to a second receiver microservice. 
     
     
       6. The system of  claim 5 , wherein the topic having a title indicative of messages intended to be received by the first data center includes a second predefined piece of text in its title. 
     
     
       7. The system of  claim 1 , wherein the first sender microservice posts the message to a topic of the first message broker having a title with a predefined prefix indicating the message is intended for a data center other than the first data center, a sender use case location, and a receiver data center in it. 
     
     
       8. A method comprising:
 monitoring, at a distributor microservice in a first data center, one or more topics of a first message broker, the one or more topics having titles indicative of messages intended to be received by a data center other than the first data center; and 
 upon detection at the distributor microservice of a message posted at the first message broker by a first sender microservice to a first topic of the one or more topics:
 identifying, based on information in the message, a destination data center and a destination landscape; 
 retrieving a destination name and destination location from a landscape configuration file accessed by the distributor microservice, using the destination data center and destination landscape; and 
 sending the message from the distributor microservice to a router microservice of the destination data center, using the retrieved destination name and destination location, the router microservice configured to post the message to a second topic in a message broker of the destination data center. 
 
 
     
     
       9. The method of  claim 8 , wherein the destination landscape is derived from the landscape configuration file using the destination data center and a sender landscape identified in a name of the first topic. 
     
     
       10. The method of  claim 8 , wherein the titles indicative of messages intended to be received by a data center other than the first data center include a predefined piece of text in the titles. 
     
     
       11. The method of  claim 8 , wherein the message further includes a use case, and wherein the method further comprises:
 retrieving a use case location from the landscape configuration file using the use case location; and 
 wherein the router microservice is further configured to determine a receiver use case location using a second landscape configuration file accessed by the router microservice and wherein the second topic includes the receiver use case location in its name. 
 
     
     
       12. The method of  claim 8 , wherein the first message broker further receives an additional message posted to a topic having a title indicative of messages intended to be received by the first data center and, in response to receiving the additional message, sends the additional message within the first data center to a second receiver microservice. 
     
     
       13. The method of  claim 12 , wherein the topic having a title indicative of messages intended to be received by the first data center includes a second predefined piece of text in its title. 
     
     
       14. The method of  claim 8 , wherein the first sender microservice posts the message to a topic of the first message broker having a title with a predefined prefix indicating the message is intended for a data center other than the first data center, a sender use case location, and a receiver data center in it. 
     
     
       15. A non-transitory machine-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
 monitoring, at a distributor microservice in a first data center, one or more topics of a first message broker, the one or more topics having titles indicative of messages intended to be received by a data center other than the first data center; and 
 upon detection at the distributor microservice of a message posted at the first message broker by a first sender microservice to a first topic of the one or more topics:
 identifying, based on information in the message, a destination data center and a destination landscape; 
 retrieving a destination name and destination location from a landscape configuration file accessed by the distributor microservice, using the destination data center and destination landscape; and 
 sending the message from the distributor microservice to a router microservice of the destination data center, using the retrieved destination name and destination location, the router microservice configured to post the message to a second topic in a message broker of the destination data center. 
 
 
     
     
       16. The non-transitory machine-readable medium of  claim 15 , wherein the destination landscape is derived from the landscape configuration file using the destination data center and a sender landscape identified in a name of the first topic. 
     
     
       17. The non-transitory machine-readable medium of  claim 15 , wherein the titles indicative of messages intended to be received by a data center other than the first data center include a predefined piece of text in the titles. 
     
     
       18. The non-transitory machine-readable medium of  claim 15 , wherein the message further includes a use case, and wherein the operations further comprise:
 retrieving a use case location from the landscape configuration file using the use case location; and 
 wherein the router microservice is further configured to determine a receiver use case location using a second landscape configuration file accessed by the router microservice and wherein the second topic includes the receiver use case location in its name. 
 
     
     
       19. The non-transitory machine-readable medium of  claim 15 , wherein the first message broker further receives an additional message posted to a topic having a title indicative of messages intended to be received by the first data center and, in response to receiving the additional message, sends the additional message within the first data center to a second receiver microservice. 
     
     
       20. The non-transitory machine-readable medium of  claim 19 , wherein the topic having a title indicative of messages intended to be received by the first data center includes a second predefined piece of text in its title.