Skip to main content

How SyncHive Exchanges Data

In this section, we'll explore the communication pathways between SyncHive, Connectors, Integrations, and external applications.

Message Life Cycle

Message Life Cycle describes the journey of data as it travels from an external application, through SyncHive, and onwards to other external applications. This process encapsulates the entire path of data transfer, transformation, storage, and delivery.

Here's how it unfolds using a practical example:

  • External Application: Data is sent from an external application to a SyncHive Connector.
  • Data Transformation: The Connector converts the external application data into a standardised Message.
  • Message to SyncHive: The Message is then sent to SyncHive.
  • Data Storage: SyncHive stores the data, then queues it for delivery.
  • Message Distribution: SyncHive forwards the Message to interested Connectors.
  • Data Transformation: The receiving Connector converts the Message to the destination external application format.
  • Destination Instance: The Connector uses Integration settings to find the destination instance.
  • Delivery to Application: The data is delivered and saved to its destination external application.

For a visual overview, refer to the diagram below:

Data Exchange Mechanisms

To meet the varied needs of data transfer, SyncHive Integrations are equipped with multiple mechanisms:

  • Events: Trigger data exchanges in response to specified events.
  • Polling: Periodically check for data updates when event-driven triggers are not feasible.
  • Filtering: Apply filters to ensure only pertinent data is transferred, minimizing excess data flow.
  • Bulk Publishing: Facilitate the transfer of large datasets efficiently with bulk data publishing capabilities.