diff --git a/docs/CM_FAQs.adoc b/docs/CM_FAQs.adoc index b8b1dd225..0029907d8 100755 --- a/docs/CM_FAQs.adoc +++ b/docs/CM_FAQs.adoc @@ -24,7 +24,7 @@ Also, is there a reason these `1000` `gets` have be done serially in one thread? ===== Answer -The stateless client has been replaced with Chronicle Engine. The stateless client is not supported in ChronicleMap 3.x. For more information, please refer to Chronicle Engine FAQ's. +The stateless client has been replaced with Chronicle Datagrid. The stateless client is not supported in ChronicleMap 3.x. For more information, please refer to Chronicle Datagrid FAQ's. For `get()s`, parallelizing will reduce costs. For `put()s`, if you have concurrency requirements, that is, multi-key lock before updating all of them, it should be in one thread. diff --git a/docs/CM_Features.adoc b/docs/CM_Features.adoc index fd8b0d2ac..7a556a2cf 100755 --- a/docs/CM_Features.adoc +++ b/docs/CM_Features.adoc @@ -129,7 +129,7 @@ Please contact us at mailto:sales@chronicle.software[sales@chronicle.software] i NOTE: For access to commercially available features please contact mailto:sales@chronicle.software[sales@chronicle.software]. == Peer projects - - https://github.com/OpenHFT/Chronicle-Engine[Chronicle Engine]. Reactive processing framework + - Chronicle Datagrid. Reactive processing framework supporting Chronicle Map as a backend. - http://vanillajava.blogspot.com/2015/09/chronicle-journal-customizable-data.html[Chronicle Journal]. Another diff --git a/docs/CM_Updates.adoc b/docs/CM_Updates.adoc index 1bfbda862..67922413b 100755 --- a/docs/CM_Updates.adoc +++ b/docs/CM_Updates.adoc @@ -18,9 +18,9 @@ Changes between Chronicle Map 3 and the previous Chronicle Map version are detai - "Listeners" mechanism fully reworked; see <>. This has a number of important consequences, most notable is that it is now possible to define "eventual-consistency" replication strategy, different from "last write wins"; any state-based CRDT. - - "Stateless clients" functionality (remote calls) is moved to https://github.com/OpenHFT/Chronicle-Engine[Chronicle Engine]. + - "Stateless clients" functionality (remote calls) is moved to Chronicle Datagrid. - - Replication is performed using https://github.com/OpenHFT/Chronicle-Engine[Chronicle Engine]. + - Replication is performed using Chronicle Datagrid. - Earlier versions of Chronicle Map had hard creation-time limits on the number of entries storable in a Chronicle Map. If the size exceeded this limit, an exception was thrown. + In Chronicle Map 3, this limitation is removed. The number of entries still has to be configured when the Chronicle Map is created, Exceeding this configured limit is possible, but discouraged. +