mirror of
https://github.com/OpenHFT/Chronicle-Map.git
synced 2021-09-13 01:26:12 +00:00
changed http://openhft.net to http://chronicle.software
This commit is contained in:
Rob Austin
@@ -1,13 +1,13 @@
|
||||
*We can help you get Chronicle up and running in your organisation, we suggest you invite us in for
|
||||
consultancy, charged on an ad-hoc basis, we can discuss the best options tailored to your individual
|
||||
requirements. - [Contact Us](http://openhft.net/support/)*
|
||||
requirements. - [Contact Us](http://chronicle.software/support/)*
|
||||
|
||||
*Or you may already be using Chronicle and just want some help - [find out more..](http://openhft.net/support/)*
|
||||
*Or you may already be using Chronicle and just want some help - [find out more..](http://chronicle.software/support/)*
|
||||
|
||||
# Chronicle Map
|
||||
|
||||
A low latency replicated Key Value Store across your network, with eventual consistency, persistence and performance.
|
||||
|
||||
|
||||
|
||||
#### Maven Artifact Download
|
||||
```xml
|
||||
@@ -60,7 +60,7 @@ Click here to get the [Latest Version Number](http://search.maven.org/#search%7C
|
||||
* [Known Issues](https://github.com/OpenHFT/Chronicle-Map#known-issues)
|
||||
* [Stackoverflow](http://stackoverflow.com/tags/chronicle/info)
|
||||
* [Development Tasks - JIRA] (https://higherfrequencytrading.atlassian.net/browse/HCOLL)
|
||||
* [Use Case Which include Chronicle Map] (http://openhft.net/products/chronicle-engine/)
|
||||
* [Use Case Which include Chronicle Map] (http://chronicle.software/products/chronicle-engine/)
|
||||
|
||||
#### Examples
|
||||
|
||||
@@ -81,7 +81,7 @@ Click here to get the [Latest Version Number](http://search.maven.org/#search%7C
|
||||
Chronicle Map implements the interface `java.util.concurrent.ConcurrentMap`, however unlike the standard
|
||||
jdk implementations, ChronicleMap is both persistent and able to share your entries accross processes:
|
||||
|
||||
|
||||
|
||||
|
||||
## When to use HashMap, ConcurrentHashMap and ChronicleMap
|
||||
#### When to use HashMap
|
||||
@@ -118,7 +118,7 @@ SharedHashMap was the old name of what is now ChronicleMap. Since the last relea
|
||||
## Getting Started
|
||||
|
||||
#### Tutorial 1 - Creating an instance of Chronicle Map
|
||||
[](http://openhft.net/chronicle-map-video-tutorial-1/)
|
||||
[](http://chronicle.software/chronicle-map-video-tutorial-1/)
|
||||
|
||||
### Simple Construction
|
||||
|
||||
@@ -126,7 +126,7 @@ To download the JAR which contains Chronicle Map, we recommend you use maven, wh
|
||||
from [Maven Central](http://search.maven.org), once you have installed maven, all you have to do is
|
||||
add the following to your projects `pom.xml`:
|
||||
|
||||
|
||||
|
||||
|
||||
```xml
|
||||
<dependency>
|
||||
@@ -595,7 +595,7 @@ If after some business logic, in our example after reading the 'issueDate' and
|
||||
|
||||
## Serialization
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
ChronicleMap stores your data into off heap memory, so when you give it a Key or Value, it will
|
||||
@@ -615,7 +615,7 @@ an example of how to do this can be found at "IntValue$$Native"
|
||||
for a single type or a number of types.
|
||||
|
||||
### Import/Export entries as JSON
|
||||
|
||||
|
||||
|
||||
ChronicleMap supports importing and exporting all the entries into a JSON encoded file.
|
||||
|
||||
@@ -665,7 +665,7 @@ your JVM to crash. Close MUST BE the last thing that you do with the map.
|
||||
|
||||
ChronicleMap supports both TCP and UDP replication
|
||||
|
||||
|
||||
|
||||
|
||||
### TCP / UDP Background.
|
||||
TCP/IP is a reliable protocol, what this means is that unless you have a network failure or hardware
|
||||
@@ -824,7 +824,7 @@ this, in other words its a bidirectional connection.
|
||||
|
||||
### Configuring Three Way TCP/IP Replication
|
||||
|
||||
|
||||
|
||||
|
||||
Below is example how to set up tcpConfig for 3 host
|
||||
|
||||
@@ -865,7 +865,7 @@ is dropped and re-established.
|
||||
|
||||
# Multiple Chronicle Maps - Network Distributed
|
||||
|
||||
|
||||
|
||||
|
||||
ChronicleMap TCP Replication lets you distribute a single ChronicleMap, to a number of servers
|
||||
across your network. Replication is point to point and the data transfer is bidirectional, so in the
|
||||
@@ -1034,7 +1034,7 @@ favoriteColourServer1.close();
|
||||
|
||||
# Stateless Client
|
||||
|
||||
|
||||
|
||||
|
||||
A stateless client is an instance of a `ChronicleMap` or a `ChronicleSet` that does not hold any
|
||||
data
|
||||
@@ -1043,7 +1043,7 @@ data
|
||||
holds all your data, the server can not it’s self be a stateless client. Your stateless client must
|
||||
be connected to the server via TCP/IP.
|
||||
|
||||
|
||||
|
||||
|
||||
The stateless client delegates all your method calls to
|
||||
the remote server. The stateless client operations will block, in other words the stateless
|
||||
@@ -1126,7 +1126,7 @@ When calling the stateless client, you will get better throughput if you invoke
|
||||
by the server. Your stateless client will block until an acknowledgement has been received from the server that
|
||||
the event was processed.
|
||||
|
||||
|
||||
|
||||
|
||||
When you are calling methods that return a value like get() this
|
||||
blocking adds no additional overhead, because you have to wait for the return value anyway,
|
||||
|
||||
Reference in New Issue
Block a user