aerospike
Advanced tools
The Aerospike Node.js client is a Node.js add-on module, written using V8.
The client is compatible with Node.js 19, 18 (LTS), 16 (LTS) and 14 (LTS). It supports the following operating systems:
The client is compatible with arm64, aarch64, and x86_64 architectures.
The Aerospike Node.js client supports all Node.js LTS releases. To download and install the latest stable version of Node.js, visit nodejs.org.
Install the necessary "development tools" and other libraries to build the client software. Reference various docker files in the repository under the docker directory for more information.
The Aerospike Node.js client is an add-on module that uses the Aerospike C client. The installation will attempt to install the pre-built binaries including dependent C client.
You can install the Aerospike Node.js client like any other Node.js module.
Node.js modules are containers of JavaScript code and a package.json, which defines
the module, its dependencies and requirements. Modules are usually installed as
dependencies of other Node.js applications or modules. The modules are installed in
the application's node_modules directory, and can be utilized within the program
by requiring the module by name.
To install aerospike as a dependency of your project, in your project directory run:
npm install aerospike
To add aerospike as a dependency in package.json, run:
npm install aerospike --save-dev
To require the module in your application:
const Aerospike = require('aerospike')
The following is very simple example how to create, update, read and remove a record using the Aerospike database.
const Aerospike = require('aerospike')
// INSERT HOSTNAME AND PORT NUMBER OF AEROPSIKE SERVER NODE HERE!
const config = {
hosts: '192.168.33.10:3000',
}
const key = new Aerospike.Key('test', 'demo', 'demo')
Aerospike.connect(config)
.then(client => {
const bins = {
i: 123,
s: 'hello',
b: Buffer.from('world'),
d: new Aerospike.Double(3.1415),
g: Aerospike.GeoJSON.Point(103.913, 1.308),
l: [1, 'a', {x: 'y'}],
m: {foo: 4, bar: 7}
}
const meta = { ttl: 10000 }
const policy = new Aerospike.WritePolicy({
exists: Aerospike.policy.exists.CREATE_OR_REPLACE,
// Timeouts disabled, latency dependent on server location. Configure as needed.
socketTimeout : 0,
totalTimeout : 0
})
return client.put(key, bins, meta, policy)
.then(() => {
const ops = [
Aerospike.operations.incr('i', 1),
Aerospike.operations.read('i'),
Aerospike.lists.append('l', 'z'),
Aerospike.maps.removeByKey('m', 'bar')
]
return client.operate(key, ops)
})
.then(result => {
console.log(result.bins) // => { i: 124, l: 4, m: null }
return client.get(key)
})
.then(record => {
console.log(record.bins) // => { i: 124,
// s: 'hello',
// b: <Buffer 77 6f 72 6c 64>,
// d: 3.1415,
// g: '{"type":"Point","coordinates":[103.913,1.308]}',
// l: [ 1, 'a', { x: 'y' }, 'z' ],
// m: { foo: 4 } }
})
.then(() => client.close())
})
.catch(error => {
console.error('Error: %s [%i]', error.message, error.code)
if (error.client) {
error.client.close()
}
})
To install library prerequisites using yum:
sudo yum group install "Development Tools"
sudo yum install openssl openssl-devel
sudo yum install python3 python3-devel
apk add build-base \
linux-headers \
bash \
libuv-dev \
openssl-dev \
lua5.1-dev \
zlib-dev \
git \
python3
yum groupinstall "Development Tools"
yum install openssl openssl-devel
yum install python3 python3-devel
To install library prerequisites using apt-get:
sudo apt -y install software-properties-common
sudo apt -y install build-essential
sudo apt -y install libssl-dev
sudo apt -y install libarchive-dev cmake rsync curl libcurl4-openssl-dev zip
sudo apt -y install python3 python3-dev python3-pip
sudo apt install zlib1g-dev libncurses5-dev libgdbm-dev libnss3-dev \
libsqlite3-dev libreadline-dev libffi-dev libbz2-dev -y
sudo apt -y install wget libtool m4 automake
To install library prerequisites using apt:
sudo apt install g++ libssl libssl-dev zlib1g-dev
Before starting with the Aerospike Nodejs Client, verify that you have the following prerequisites:
Openssl Library
The below example shows how to install the Openssl library.
brew install openssl
unlink /usr/local/opt/openssl
# Change the below linking based on openssl version and installation path
ln -s /usr/local/Cellar/openssl@x/y.z/ /usr/local/opt/openssl
If you are looking upgrade switch from openssl@1 or an older version of openssl@3, add these variables to your .bashrc, .profile, or .zshrc file.
export PATH="/usr/local/bin/:/usr/local/opt/openssl/bin:$PATH"
export LDFLAGS="-L/usr/local/opt/openssl/lib"
export CPPFLAGS="-I/usr/local/opt/openssl/include"
export EXT_CFLAGS="-I/usr/local/opt/openssl/include"
Afterwards, source the file that was changed and confirm the desired openssl version is installed
source ~/.bashrc
source ~/.profile
source ~/.zshrc
openssl version
For 4x client support, install openssl@1.1 version.
LIBUV Library
The example below shows how to install the LIBUV library.
brew install libuv
unlink /usr/local/opt/libuv
# Change the below linking based on libuv version and installation path
ln -s /usr/local/Cellar/libuv/1.44.1_1/ /usr/local/opt/libuv
When using a cloned repository, install aerospike as a dependency of your application. Instead of referencing the module by name, you reference it by path.
To clone the repository use the following command:
git clone --recursive git@github.com:aerospike/aerospike-client-nodejs.git
Make sure to build the C client before doing npm install variants Run the following commands to build the C client:
./scripts/build-c-client.sh
To install the module as a dependency of your application, run the following in the application directory:
npm install --unsafe-perm --build-from-source
To require it in the application:
const Aerospike = require('aerospike')
Access the client API documentation at: https://docs.aerospike.com/apidocs/nodejs. This documentation is built from the client's source using JSDocs v3 for every release.
The API docs also contain a few basic tutorials:
async/awaitA variety of additional example applications are provided in the
examples directory of this repository.
Access backward incompatible API changes by a release at: https://developer.aerospike.com/client/nodejs/usage/incompatible.
The Aerospike Node.js client library follows semantic versioning. By Aerospike versioning guidelines, changes which may break backwards compatibility are indicated by an increase in the major version number. Minor, or patch releases, which are incremented only the second and third version number, are always backwards compatible.
The client includes a comprehensive test suite using Mocha. The tests can be found in the repository under test directory.
Before running the tests, you need to update the dependencies:
npm update
To run all the test cases:
npm test
Note: make sure your server has TTL enabled for the test namespace (Namespace Retention Configuration) to allow all tests to run correctly.
To run the tests and also report on test coverage:
npm run coverage
Benchmark utilities are provided in the repository under benchmarks directory. See the benchmarks/README.md for details.
The Aerospike Node.js Client is made available under the terms of the Apache License, Version 2, as stated in the LICENSE file.
Individual files may be made available under their own specific license, all compatible with Apache License, Version 2. Refer to individual files for details.
[5.2.1]
New Features
Improvements
Bug Fixes
FAQs
Aerospike Client Library
The npm package aerospike receives a total of 2,262 weekly downloads. As such, aerospike popularity was classified as popular.
We found that aerospike demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.