Page History

...

1. The concept of participant replicas into ACM-R and the Participant Intermediary
2. A lightweight mechanism for replica update between replicas and ACM-R. Every time a replica changes its data, the change is reported to ACM-R and ACM-R updates all other replicas for that participant

Image Added

In this solution:

1. Participant Design backward compatibility is preserved, there is no change to the participant intermediary interface for participant implementations
2. Participant Configuration Backward compatibility is preserved, apart from a new "replicas" parameter (optional, default is 1), there is no change to participant configuration
3. ACM-R introduces a new REST API for replica management
4. ACM-R is made HA so that it itself can scale

...