...
- Multiple participant replicas possible - it can deal with messages across many participants
- All participants should have same group-id in kafka
- All should have the same participant-id.
Disadvantages of DB use
- The Participant as a concept envisages an extremely lightweight mechanism, which can be deployed as a very lightweight plugin into the runtime entity implementing a participant
- Introducing a database into the participant means that participant becomes a heavyweight plugin with cross participant and participant/acm-r configuration required
- There are multiple sources of truth for participant and element data, the ACM-R DB and the this new participant DB have duplicated data
- Participant configuration is no longer transparent to the participant implementing component, having a DB for each participant forces orthogonal configuration across participant implementing components
- Configuration of components implementing participants becomes much more complex, the components must manage the participant replication
- The replication mechanism enforces the use of an additional 3pp, the database
Solution 4: Distributed Cache
...