[ROOT] / doc / DocFrag / ARCCore.ARConcepts.CoreDBSynchronization

EnumMemberAttribute

The concept of how multiple CoreDB instances synchronizes their data.

TODO: The inherent possibility in AgoRapide of having multiple CoreDB nodes
TODO: means that synchronization between these nodes must be considered.
TODO: As of Apr 2020 the most critical issue being identified is probably how to re-synchronize nodes after some
TODO: period of offline status / network outage and similar.
TODO: Also a mechanism for anointing a master-node and similar must be implemented.

TODO: There is also the issue of what happens when the core itself is unavailable. In principle the clients are perfectly
TODO: capable of caching data, and sending it as soon as the core gets online again, but then there is the issue of ordering data
TODO: from the different client nodes correctly into the property stream.
TODO: One possible solution to this issue might be to just state that it is unsolved and that such cached data will be put into the
TODO: property stream without any coordination / ordering.

See also MultipleConnectionUsage and Sharding.

Edit

Generated 2025-10-31 04:55:31.992 UTC