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

doco: Engine -> Datagrid

Browse Source
This commit is contained in:
Jerry Shea
2020-05-14 08:29:27 +10:00
parent 9b1d3f6393
commit 528e09bd0c
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CM_FAQs.adoc
+1 -1
View File
@@ -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.
docs/CM_Features.adoc
+1 -1
View File
@@ -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
docs/CM_Updates.adoc
+2 -2
View File
@@ -18,9 +18,9 @@ Changes between Chronicle Map 3 and the previous Chronicle Map version are detai
- "Listeners" mechanism fully reworked; see <<CM_Tutorial_Behaviour.adoc#,Behaviour Customization>>. 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. +