...
As an example, we may have one system for taking and managing orders and another system performing our customer support activities. In this scenario, perhaps these two systems are considered best of breed and it is critical to our enterprise needs to use them in combination rather than a suite which supports both functions and uses shared data structures. So, instead we are using the bi-directional pattern to share a dataset to facilitate the utilization of both of these systems, and maintaining a consistent real-time view of the data in both applications.
Value of Bi-Directional
The Bi-directional sync Directional synchronization pattern can be both an enabler and a savior depending on the circumstances that justify its needscenarios in which it is being deployed. If you your systems have two or more independent (and isolated) representations of the same realitydata, you then we can use utilize bi-directional sync pattern to optimize your processes.
On the other hand, you we can use deploy the bi-directional sync to take you pattern to transition our system from a suite of products that work well together — (but may not be the best of breed at their own individual function — ), to a suite that you hand pick and implementation has been crafted to integrate together using an enterprise integration platform like MuleSoft’s Anypoint Platform.
...
(like MuleSoft, Boomi, Informatica, Oracle, TIBCO).
Usefulness of Bi-Directional
The need for a bi-directional sync integration application is synonymous with wanting object representations of reality to be comprehensive and consistent. For example, if you want a single view of your customer, you can solve that manually by giving everyone access to all the systems that have a representation of the notion of a customer. But a more efficient solution is to list out which fields need to be visible for that customer object in which systems and which systems are the owners.
...