As your enterprise grows and becomes global, your applications will also grow and evolve in complexity. Eventually, those applications will be distributed across multiple sites, which includes multiple public and private clouds as well as legacy data centers—driving the need to intelligently share information between multiple locations and interfaces.
Providing this sort of extensive, continuous operation can be achieved using a Dynamic Message Routing (DMR) network, or event mesh, to automatically connect all those sites and exchange subscription information. In this article, we will see how to Configure DMR Bridges. Before we get into details, let us learn a little bit about Event Mesh and enabling Event Mesh through DMR Bridges.
An event mesh is a customizable and dynamic infrastructure layer for distributing events among decoupled applications, cloud services and devices. It allows event communications to be governed, flexible, reliable and fast. An event mesh is created and empowered through a network of interconnected event brokers.
In other words, it allows events from one application, no matter where these applications are deployed, to be dynamically routed and received by any other application. This layer has a network of event brokers.
Enabling Event Mesh through Dynamic Message Routing (DMR) Bridges
DMR qualifies an event mesh by linking PubSub+ event brokers within or between environments. This lets you to scale capacity within an environment or link applications across various environments.
How to configure DMR Bridges?
Follow the steps below to configure static bridge
Published from gcp-singapore instance
Figure 1Consumed at azure-virginia instance
Try sending message streams from one instance to another and it should work without adding a subscription to any of the instances.