The Hazelcast Node.js client, currently at version 5.6.0, provides a robust, promise-based API for connecting Node.js applications to a Hazelcast cluster, a distributed computation and storage platform. It enables developers to interact with distributed data structures like Maps, Queues, and Topics, facilitating real-time stream processing and in-memory data grid functionalities. The client supports native JavaScript objects and ships with TypeScript types, ensuring a smooth development experience. Releases are frequent, with significant updates often introducing new features such as stable Compact Serialization in v5.2.0 and SQL JSON support, while maintaining backward compatibility where possible. Its key differentiators include seamless integration with the Hazelcast ecosystem, resilience through data rebalancing and backups across cluster members, and dynamic scalability for handling varying data and computational loads, from edge devices to large cloud deployments.
npm install hazelcast-clientVerified import paths — ran on the pinned version, not inferred.
Demonstrates connecting to a local Hazelcast cluster, creating/accessing a distributed map, performing put and get operations, and gracefully shutting down the client. Includes basic error handling and TypeScript types.
Before upgrading to 5.6.0+, thoroughly test compact serialized data reading in a staging environment. If issues arise, ensure consistent client and server versions, or migrate data using a compatible serialization method.
Update all calls from `client.getSqlService()` to `client.getSql()`.
Ensure both your Hazelcast Node.js client and Hazelcast server versions are 5.0 or newer for full SQL compatibility with these date/time types.
Always install v5.0.1 or a later version (e.g., `npm install hazelcast-client@latest`) instead of v5.0.0.
If using Compact Serialization, ensure your Hazelcast server is version 5.2 or newer to guarantee compatibility and stability.
Verify that a Hazelcast cluster member is running and accessible at the `clusterMembers` addresses specified in your `ClientConfig`. Common default is `127.0.0.1:5701`. Check firewalls if connecting to a remote server.
Rename `client.getSqlService()` to `client.getSql()` as the method was renamed in version 5.0.0.
Wrap your client initialization and operations in an `async` function, then call that function. For top-level awaiting in modules, ensure your Node.js version supports it and your `package.json` is configured for ESM.
No dependency data recorded yet.