/ doc / DocFrag / ARCCore.ARConcepts.CoreDBSynchronization / Description

Description

Edit keys at this level only

= The concept of how multiple -CoreDB- instances synchronizes their data.0x000D0x000A0x000D0x000ATODO: The inherent possibility in AgoRapide of having multiple -CoreDB- nodes0x000D0x000ATODO: means that synchronization between these nodes must be considered.0x000D0x000ATODO: As of Apr 2020 the most critical issue being identified is probably how to re-synchronize nodes after some0x000D0x000ATODO: period of offline status / network outage and similar.0x000D0x000ATODO: Also a mechanism for anointing a master-node and similar must be implemented.0x000D0x000A0x000D0x000ATODO: There is also the issue of what happens when the core itself is unavailable. In principle the clients are perfectly0x000D0x000ATODO: capable of caching data, and sending it as soon as the core gets online again, but then there is the issue of ordering data0x000D0x000ATODO: from the different client nodes correctly into the property stream.0x000D0x000ATODO: One possible solution to this issue might be to just state that it is unsolved and that such cached data will be put into the0x000D0x000ATODO: property stream without any coordination / ordering.0x000D0x000A0x000D0x000ASee also -MultipleConnectionUsage- and -Sharding-.

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Generated 2025-06-30 13:02:15.870 UTC