23
23
[ Hazelcast] ( https://hazelcast.com/ ) is an open-source distributed in-memory data store and computation platform that
24
24
provides a wide variety of distributed data structures and concurrency primitives.
25
25
26
- Hazelcast Node.js client is a way to communicate to Hazelcast IMDG clusters and access the cluster data.
26
+ Hazelcast Node.js client is a way to communicate to Hazelcast clusters and access the cluster data.
27
27
The client provides a Promise-based API with a builtin support for native JavaScript objects.
28
28
29
29
## Installation
30
30
31
31
### Hazelcast
32
32
33
- Hazelcast Node.js client requires a working Hazelcast IMDG cluster to run. This cluster handles the storage and
33
+ Hazelcast Node.js client requires a working Hazelcast cluster to run. This cluster handles the storage and
34
34
manipulation of the user data.
35
35
36
- A Hazelcast IMDG cluster consists of one or more cluster members. These members generally run on multiple virtual or
36
+ A Hazelcast cluster consists of one or more cluster members. These members generally run on multiple virtual or
37
37
physical machines and are connected to each other via the network. Any data put on the cluster is partitioned to
38
38
multiple members transparent to the user. It is therefore very easy to scale the system by adding new members as
39
- the data grows. Hazelcast IMDG cluster also offers resilience. Should any hardware or software problem causes a crash
39
+ the data grows. Hazelcast cluster also offers resilience. Should any hardware or software problem causes a crash
40
40
to any member, the data on that member is recovered from backups and the cluster continues to operate without any
41
41
downtime.
42
42
@@ -48,7 +48,7 @@ docker run -p 5701:5701 hazelcast/hazelcast:4.1.1
48
48
```
49
49
50
50
You can also use our ZIP or TAR [ distributions] ( https://hazelcast.com/open-source-projects/downloads/ )
51
- as described [ here] ( DOCUMENTATION.md#121-setting-up-a-hazelcast-imdg- cluster ) .
51
+ as described [ here] ( DOCUMENTATION.md#121-setting-up-a-hazelcast-cluster ) .
52
52
53
53
### Client
54
54
@@ -84,7 +84,7 @@ await client.shutdown();
84
84
> Refer to the [ Code Samples section] ( https://github.com/hazelcast/hazelcast-nodejs-client/tree/master/code_samples )
85
85
> to see samples with the complete code.**
86
86
87
- If you are using Hazelcast IMDG and the Node.js client on the same machine, the default configuration should work
87
+ If you are using Hazelcast and the Node.js client on the same machine, the default configuration should work
88
88
out-of-the-box. However, you may need to configure the client to connect to cluster nodes that are running on
89
89
different machines or to customize client properties.
90
90
@@ -147,7 +147,7 @@ We encourage any type of contribution in the form of issue reports or pull reque
147
147
148
148
For issue reports, please share the following information with us to quickly resolve the problems.
149
149
150
- * Hazelcast IMDG and the client version that you use
150
+ * Hazelcast and the client version that you use
151
151
* General information about the environment and the architecture you use like Node.js version, cluster size,
152
152
number of clients, Java version, JVM parameters, operating system etc.
153
153
* Logs and stack traces, if any.
@@ -180,7 +180,7 @@ Following command starts the tests:
180
180
npm test
181
181
```
182
182
183
- Test script automatically downloads ` hazelcast-remote-controller ` and Hazelcast IMDG . The script uses Maven to download those.
183
+ Test script automatically downloads ` hazelcast-remote-controller ` and Hazelcast. The script uses Maven to download those.
184
184
185
185
In order to run specific tests, you can give a pattern to the test command like the following:
186
186
0 commit comments