immudb-node implements a grpc immudb client. A minimalist API is exposed for applications while cryptographic verifications and state update protocol implementation are fully implemented by this client. Latest validated immudb state may be keep in the local filesystem when initialising the client with the rootPath option, please read immudb research paper for details of how immutability is ensured by immudb.
immudb-node assumes an already running immudb server. Running immudb
is quite simple, please refer to the
following link for downloading and running it: https://docs.immudb.io/quickstart.html
Just include immudb-node as a dependency in your project:
const ImmudbClient = require('immudb-node')
immudb-node supports the latest immudb release.
Check out some examples
The following code snippets shows how to create a client.
Using default configuration:
const config = {
address: '127.0.0.1:3322',
rootPath: '.',
}
ImmudbClient(config, (err, cl) => {
if (err) {
return console.log(err)
}
// Interact with the client.
})
Use login
and logout
methods to initiate and terminate user sessions:
try {
await cl.login({ username: 'usr1', password: 'pwd1' })
// Interact with immudb using logged user.
await cl.logout()
} catch (err) {
console.log(err)
}
Or with callbacks
cl.login({ username: 'usr1', password: 'pwd1' }, (err, res) => {
if (err) {
return console.log(err)
}
// Interact with immudb using logged user.
cl.logout(null, (err, res) => {
if (err) {
return console.log(err)
})
// Logged out.
})
Creating a new database is quite simple:
cl.createDatabase('db1')
Specify the active database with:
cl.useDatabase('db1')
immudb provides read and write operations that behave as a traditional
key-value store i.e. no cryptographic verification is done. This operations
may be used when validations can be post-poned:
let res = await cl.set({ key: 'key1', value: 'value1' })
console.log(res.index)
res = await cl.get({ key: 'key1' })
console.log(res.key, res.value, res.index)
immudb provides built-in cryptographic verification for any entry. The client
implements the mathematical validations while the application uses as a traditional
read or write operation:
try {
let res = await cl.safeSet({ key: 'key1', value: 'value1' })
console.log(res.index)
res = await cl.safeGet({ key: 'key1' })
console.log(res.key, res.value, res.index)
} catch (err) {
if (err.clientErr == cl.proofErr) {
// Proof does not verify.
}
console.log(err)
}
Transactional multi-key read and write operations are supported by immudb and immudb-node.
Atomic multi-key write (all entries are persisted or none):
req = {
skvList: [{
key: 'key1',
payload: 'value1',
timestamp: Math.floor(Date.now()/100),
},{
key: 'key2',
payload: 'value2',
timestamp: Math.floor(Date.now()/100),
}]
}
res = await cl.setBatchSV(req)
Atomic multi-key read (all entries are retrieved or none):
req = {
keys: [{
key: 'key1',
},{
key: 'key2',
}],
}
res = await cl.getBatchSV(req)
To programatically close the connection with immudb server use the shutdown
operation:
cl.shutdown()
Note: after shutdown, a new client needs to be created to establish a new connection.
We welcome contributions. Feel free to join the team!
To report bugs or get help, use GitHub’s issues.