For a product manufacturing company these lines of business might be: Manufacturing, Inventory, Shipping, Sales, Finance, and Human Resources. Keep this at a high level, not a specific application or application team, but along the lines of product groups or cost centers within your organization. List all the foundational application domains- usually the lines of business (LoBs)-within your organization. Then also there is regional presence in primary and possible secondary cloud providers. Theses will be the sites.įor example, in the diagram below there are primarily Europe (EU), North America, (NA) Data Centers. List all the data centers or cloud provider regions where applications run or will run. The goal should be to create homogeneous clusters, and there are a number of ways to do this, but a first approach would be to consider the sites and lines of business (LoBs) of your organization. The first step to building an event mesh is to define what constitutes a cluster. For an easy way to catalog and visualize event-related data, take a look at PubSub+ Event Portal's Catalog. This catalog allows consumers to subscribe to the data they would like to consume. Along with a topic hierarchy that conforms with the Topic Architecture Best Practices, you also need a catalog of available data as described by the topics. Proper topics also allow administrative control of data. To achieve this, you must define a topic hierarchy that allows publishers to properly describe the data they are creating without conflicts. The main advantage of an event mesh is unlocking your data from silo-ed systems making that data easy to use. Manage data access for applications outside the event mesh.Consider how you want your clusters to grow.
This step defines the interactions between the clusters and their underlying applications.
This doesn't mean that you don't need an event mesh, just that your event mesh might be much simpler to visualize, and you might not require much help getting started. This example may not be reflective of your organization. In the example below we are going to look at a complex problem of building an event mesh for a large global organization. This is discussed in detail in DMR Subscription Propagation and Data Forwarding. In addition, you should also understand how subscription propagation works. Before you read these best practices, ensure that you also understand the event mesh core concepts described in DMR Terminology. It also discusses Solace's recommendations for configuring certain aspects of your event mesh.
DMR CONTROL CENTER MONITOR HOW TO
This section explores some examples that show how to deploy an event mesh using Dynamic Message Routing (DMR).
0 kommentar(er)
