...
Usefulness of Bi-Directional
The need requirement for a bi-directional sync integration application is synonymous with wanting object representations the need for an object’s representation of reality to be both comprehensive and consistent. For example, if you want we need a single view of your customer, you can solve that source of truth of our, it can be provided 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 visibility for that a customer object in which each systems and identify which systems are the owners.
Most enterprise systemsapplications have a way method to extend objects such that you can modify the customer object data structure to include those fields. Then, you can create integration applications either as point-to-point applications (using with a common integration platform) if it’s for a simple solution, or a more advanced routing system like a utilize the pub/sub or queue routing model if for a more advanced routing system when there are multiple systems at play.
For example, a salesperson should needs to know the status of a an order delivery, but they don’t need to know at which warehouse the delivery iswas made. Similarly, the a delivery person needs to know the customer name of the customer that the delivery is for without needing for delivery without the need to know how much the customer paid for it. Through the use of Bi-directional synchronization allows . both of those people them to have a real-time view of the same customer through and access the lens unique content they need.