...
Therefore today, for the three types of data above, the ACM-R database has the state of the participant. This means that creation of participant replicas is rather trivial. We leave the current data handling mechanism in place, introduce the concept of participant replicas in ACM-R, and introduce data synchronization across participant replicas.
In this solution:
- Participant Design backward compatibility is preserved, there is no change to the participant intermediary interface for participant implementations
- Participant Configuration Backward compatibility is preserved, apart from a new "replicas" parameter (optional, default is 1), there is no change to participant configuration
- ACM-R introduces a new REST API for replica management
- ACM-R is made HA so that it itself can scale
...