neatComponents is the hybrid-cloud database engine that powers clearString. | ||
Previous page | Scaling and Clustering | Next page |
Introduction to Intersite Communication |
![]() | ![]() |
This section describes the features provided to facilitate the communication of data between sites. Communication between sites is key to:
In describing the processes involved we will be referring to two sites: Site A This is the site that starts a process by sending data. Site B This is the site that receives this data. In a real-world scenario more than two sites can be communicating with each other, but each individual communication will be between two sites You may also have communication working in both directions, so the roles of the two sites are reversed depending on the particular process flow. Communication process Security is inherent in the communication, so before any communication can occur API keys and secrets need to be set up to ensure connections are only accepted from authorised counterparties. Diagnostics fields are provided to allow for communication errors or misconfigurations to be understood and corrected. Once security is set up. the communication process involves:
The following pages (listed on the right) detail the configuration required. |
|