...
If ACM-R is informed by a replica that an Implementing Component changed composition element properties, Participant Synchronization synchronizes these changes to all other Participant Intermediary replicas.
In this solution:
- We will preserve 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 configurationversion backward compatibility will not be preserved because we need to pass replica information in the registration and operational messages, all participants will have to be upgraded to the new version.
- ACM-R introduces a new REST API for replica management
- ACM-R is made HA so that it itself can scale
- We can use Kafka load balancing on the participants and get the load balancing functionality for nothing
- A new Kafka topic is used for synchronization
...