Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

Update following discussion with RA.

Browse Source
This commit is contained in:
Neil Clifford
2017-10-26 11:34:27 +01:00
parent 22a41fd235
commit 578f6694dd
3 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ReadMe.adoc
+3 -1
View File
@@ -81,7 +81,9 @@ Replication is multi-master, lock-free, redundant, deterministic, and eventually
The writer can optionally wait for replication to occur across nodes or regions.
NOTE: See <<docs/CM_Replication.adoc#,Chronicle Map Replication>> for more information.
NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software]. +
See <<docs/CM_Replication.adoc#,Chronicle Map Replication>> for more information.
'''
== Documentation
docs/CM_Features.adoc
+3
View File
@@ -34,6 +34,9 @@ applications, such as trading and financial market applications.
doesn't sustain write rates.
NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software].
NOTE: See <<CM_Replication.adoc#,Chronicle Map Replication>> for more information.
**Chronicle Map** has two meanings:
docs/CM_Replication.adoc
+7 -1
View File
@@ -24,7 +24,10 @@ For more information on the stress test see <<CM_Replication_Stress_Test.adoc#,C
= Replication
Chronicle Map Replication is a multi-master replicated data store. Chronicle Map supports both TCP and UDP replication
Chronicle Map Replication is a multi-master replicated data store. Chronicle Map supports both TCP and UDP replication.
NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software].
image::http://openhft.net/wp-content/uploads/2014/07/Chronicle-Map-TCP-Replication_simple_02.jpg[TCP/IP Replication]
@@ -44,6 +47,9 @@ We are careful not to swamp your network with too much TCP/IP traffic. We do thi
== How Chronicle Map Replication works
Chronicle Map provides multi-master hash-map replication. This means that each remote map mirrors its changes over to another remote map. Neither map is considered to be the master store of data. Each map uses timestamps to reconcile changes.
NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software].
We refer to an instance of a remote map as a **node**. Each node can be connected to up to 128 other nodes.
The data that is stored locally in each node becomes eventually consistent. So changes made to one node, for example by calling `put()`, will be replicated over to the other node.