Yes, Exalate supports both one-way and two-way synchronization depending on how you configure your sync scripts.
Two-way synchronization (bidirectional sync)
Two-way sync is the default pattern where changes made on either side propagate to the other, keeping both systems continuously updated. This bidirectional approach works well when teams on both sides actively work on synchronized items and need to see each other's updates in real time.
One-way synchronization
One-way synchronization flows data in a single direction, typically used when one system acts as the source of truth and the other consumes updates without sending changes back. You implement one-way sync by configuring only the outgoing script on the sending side and the incoming script on the receiving side, without creating the reverse flow. For example, development teams might push status updates to a customer portal system that displays information but doesn't update back to the development environment.
Hybrid synchronization patterns
You can also create hybrid patterns where some fields sync bidirectionally while others move in only one direction. A connection might sync comments and attachments two-way so teams can collaborate, but only accept status and priority updates from one designated side that controls those attributes. This granular control lets you design synchronization patterns that match your actual business processes and governance requirements.
How Exalate’s autonomous control supports synchronization patterns
The autonomous control architecture supports these patterns naturally. Each side independently defines what to send in outgoing scripts and what to accept in incoming scripts. For true one-way sync, the receiving side simply doesn't populate any replica fields in its outgoing script, so nothing flows back. This approach maintains the flexibility to adjust synchronization direction later without requiring coordination with the other side.