Skip to content


Folders and files

Last commit message
Last commit date

Latest commit



61 Commits

Repository files navigation

Connector - high-level Tarantool driver

Connector implements Tarantool binary protocol and exposes nice interface to access Tarantool.

Connector uses Transport to compose and parse request and response headers.


npm install tarantool

Notes on Tarantool Connector

Connector hides protocol-related stuff under the hood but there are things to know about before using it.

Tarantool database consists of Spaces (tables) and Tuples (rows). Spaces have no name, only numeric id.

This module provides three interfaces — Connection, Mapping and Space.

Connection contains methods to send all kinds of requests, but arguments (and results) are binary Tuples — not usable.

Mapping knows how to convert Object to Tuple and vice versa (thanks to spec) and Space is a Mapping with specified space id.

Call ping on Connector, call on Mapping and insert, select, update, delete on Space.

Object-to-Tuple binding specification — spec

There are three inner types in Tarantool storage: int32, int64 and buffer (octet string). All integers (options, flags, fields, space ids) are unsigned.

Connector can encode some pseudo-types:

  • int32: Unsigned 32-bit integer.
  • int53: Stored as internal int64. A native unsigned JS Number limited to 53 bit, stored natively without lost of significance.
  • int64: Accepts and returns BigNum objects from bignum.
  • buffer: Raw binary buffer.
  • string: Stored as buffer UTF-8 string.
  • object: Stored as buffer UTF-8 string with JSON content.

In order to use custom type, instead of providing it's name, pass object having pack: (value) -> buffer and unpack: (buffer) -> value methods as in example below.

Build spec object to map Object and Tuples to each other. Tarantool knows nothing about field names or types and Mapping maps them depending on spec.

Example of valid spec:

spec = id: 'int32', name: 'string', flags: 'object', smth_hard: {pack: ((value) -> ...), unpack: ((buffer) -> ...)}

We specify three field-related things: order, name and type. spec tells Mapping which place should every field take and how to convert it.

Use any string containing '32' to specity int32 type, same for 53 and 64



tc stands for Tarantool Connection

# create Connection using default Transport
# default port is 33013
tc = Tarantool.connect port, host, callback
# OR create Connection using Transport, any object, with `request(type, body, callback)`
# tc = new Tarantool transport

# make use of connection
tc.insert space, tuple, [flags,] callback space, tuples, [index, [offset, [limit,]]] callback
tc.update space, tuple, [operations, [flags,]] callback
tc.delete space, tuple, [flags,] callback proc, tuple, [flags,] callback callback
  • space, flags, offset and limit are Integers
  • space is Space number
  • flags is optional field, possible values are stored in Tarantool.flags in camelCase, e.g. Tarantool.flags.returnTuple
  • offset and limit are optional, use them to specify ammount of returned with select
  • tuples is an Array of tuples
  • tuple is an Array of Fields, each Field is Buffer
  • proc is a String
  • operations is an Array of operation, they are constructed via Mapping or Space methods (see below)
  • callback is a Function that is called as callback (returnCode, body) where body is an Array of tuples or a Number or an error string if returnCode is non-zero.


Use Mapping to access several spaces with similar structure.

Mapping API:

# creating mapping with specified spec
mapping = tc.mapping spec

# forgetting about tuples
mapping.insert space, object, [flags,] callback space, objects, [index, [offset, [limit,]]] callback
mapping.update space, object, [operations, [flags,]] callback
mapping.delete space, object, [flags,] callback proc, object, [flags,] callback

callback will be called as callback (returnCode, body) where body is an Array of Objects or a Number or an error string if returnCode is non-zero.

# creating operations list — see below
mapping.assign argument
mapping.add argument
mapping.and argument
mapping.xor argument
mapping.or argument
mapping.delete argument
mapping.insertBefore argument
mapping.splice spliceArgument

spliceArgument is a Hash (Object) with three keys: string (String), offset (Number) and length (Number).

argument is a Hash (Object) with single key.


Space incapsulates Mapping and space number to give you shortest API:

# creating Space with spec
space = space, spec
# OR with mapping
# mapping = tc.mapping spec
# space = space, mapping

space.insert object, [flags,] callback objects, [index, [offset, [limit,]]], callback
space.update object, [operations, [flags,]] callback
space.delete object, [flags,] callback

# creating operations list
space.assign argument
space.add argument
space.and argument
space.xor argument
space.or argument
space.delete argument
space.insertBefore argument
space.splice spliceArgument


Tarantool's update deals with "operations" — atomic field actions.

Here's an example:

spec = id: 'i32', name: 'string', winner: 'i32'
userSpace = 2, spec
operations = [
    userSpace.or winner: 1
    userSpace.splice name: offset: 0, length: 0, string: '[Winner] '
userSpace.update { id: userId }, operations, ->
    console.log 'winner now has [Winner] tag before his name'


  • check if Buffer.concat is fast enough, if it is slow - replace with array of buffers, concat only before transport.request
  • check argument type in operations
  • catch socket errors and reconnect
  • write about Tarantool keys and multi-object select
  • write tests

Bugs and issues

Bug reports and pull requests are welcome.


Tarantool Connector for node.js is published under MIT license.


A node.js connector for Tarantool <= 1.5