Connectors & Integrations
Building on the foundational understanding of SyncHive's hub & spoke architecture, let's dive deeper into how Connectors and Integrations operate within this framework, and how they facilitate data exchange between SyncHive, the hub, and the Connectors, the spokes, extending outward from the hub to interface with external applications.
Connectors
A Connector is a reusable piece of integration logic that SyncHive uses to connect with external systems like SAP ERP, Salesforce, or AWS S3. Connectors are not confined to specific instances of those applications; rather, they ensure that data can be accurately sent to and received from the general application environment. They require initial setup within SyncHive to establish the communication pathway, ensuring that data can be transferred reliably, consistently, and in accordance with SyncHive’s integration framework.
Integrations
Integrations provide the configuration layer that determines how a Connector operates against a specific instance of an external system. They dictate how a Connector interacts with specific instances of an external application, such as directing data to a specific Salesforce environment or an AWS S3 bucket. This level of detail includes configuring instance-specific information like IDs and webhook keys, ensuring that the data reaches its correct destination.
Connectors & Integrations in Practice
The hub & spoke model allows Connectors and Integrations to be added or modified independently, keeping existing data flows stable. SyncHive operates as the central point where data is processed and routed through the configured Connectors and Integrations to each connected application.
In practice, SyncHive engages with a Connector rather than the external system directly. Taking Salesforce as an example, the Salesforce Connector acts as an intermediary, allowing SyncHive to interface with Salesforce. It is through specific Integrations, tailored for different Salesforce regional instances, that detailed instructions are provided on the precise locations within Salesforce where data should be sent or received from.
Refer to the diagram below: