Setting up links between morphic services to share data between data elements is a method to tell the network the relationship and how data are transformed in the network. However, data does not flow in the network until there is a recipient (client) that may receive the data.
The linking path may be complex and is also possible to organize the services into a neural net or distributed ledgers.
The data is transferred peer to peer between the objects ghosts. Based on how you have configured Synx BIOS the transformation follows the linking path in the network or the predicates from each service is running inside the ghost entity for edge performance. Synx can also be configured to follow the path and route data to the URL (IP) of each domain.
The Real Time Web uses SynxBIOS that offers event driven distribution of data and events up and down the network layers. This enables the network to be dynamic. While clients receive data from the network the linking and service model can be changed without the client to be disconnected.
The service providers in the linking path between primary and secondary service may not access the data that is transferred between object A and object B unless they are granted access.