Skip to content
Javascript driver for C8
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

C8 JavaScript Driver

The official C8 JavaScript client.


With Yarn or NPM

yarn add jsc8
## - or -
npm install jsc8

If you want to use the driver outside of the current directory, you can also install it globally using the --global flag:

npm install --global jsc8

From source

git clone
cd jsC8
npm install
npm run dist


Latest Documentation

jsc8 tutorial

This is a short tutorial to get started with jsc8.

Getting a handle

In order to do anything useful we need a handle to an existing C8 fabric. Let’s do this by creating a new instance of Fabric using a connection string:

fabric = new Fabric("");

This connection string actually represents the default values, so you can just omit it:

fabric = new Fabric();

If that’s still too verbose for you, you can invoke the driver directly:

fabric = require('jsc8')();

The outcome of any of the three calls should be identical.

Creating a Geofabric

A Fabric consists of one or many individual "geofabrics" with which you can do anything. Each geofabric is a cluster of one or more physical locations.

We don’t want to mess with any existing data, so let’s start by creating a new geofabric called “myfabric”:

await fabric.createFabric("myfabric", [{ username: 'root' }], { dcList: "" });

Because we’re trying to actually do something on the server, this action is asynchronous. All asynchronous methods in the C8 driver return promises but you can also pass a node-style callback instead.

Keep in mind that the new fabric you’ve created is only available once the callback is called or the promise is resolved.

Switching to the new fabric

We’ve created a new fabric, but we haven’t yet told the driver it should start using it. Let’s change that:


You’ll notice this method is executed immediately. The handle “fabric” now references the “myfabric” geofabric instead of the (default) “_system” geofabric it referenced before.

Creating a tenant

const guestTenant = fabric.tenant("mytenant");
await guestTenant.createTenant("my-password");

Here a tenant named "mytenant" will be created with password as "my-password". As in the case for creating a fabric, this call is also asynchronous.

Switching to the new tenant

We’ve created a new tenant, but we haven’t yet told the driver it should start using it. Let’s change that:


Again like in fabric, this will be executed immediately. The handle "fabric" now references the "mytenant" tenant instead of the (default) "_mm" tenant it referenced before.

Another handle

Collections are where you keep your actual data. There are actually two types of collections but for now we only need one.

Like fabrics, you need a handle before you can do anything to it:

collection = fabric.collection('firstCollection');

Again notice that it executes immediately. Unlike fabrics, the collection doesn’t have to already exist before we can create the handle.

Creating a collection

We have a handle but in order to put actual data in the collection we need to create it:

await collection.create();

Listening to collection changes in realtime

Collections provide with a onChange method, with which you can see all the changes happening to an existing collection in realtime.

      onmessage: (msg) => console.log("message=>", msg),
      onopen: () => {
        console.log("connection open");
        //manipulate the collection here
      onclose: () => console.log("connection closed")
    }, "");

    async collectionManipulation(collection) {
        const doc = {
        _key: "employees",
        firstname: "Bruce",
        lastname: "Wayne"
        try {
        } catch (e) {
        console.log("Could not save document", e);

        try {
        await collection.update("employees", { email: '' });
        } catch (e) {
        console.log("Could not update document", e);

        try {
        await collection.remove('employees');
        } catch (e) {

Now whenever you manipulate the collection realtime messages can be seen.

Note: Remember to close the onChange's listeners else you will have have a memory leak. Use closeOnChangeConnection for this purpose.

Creating a document

What good is a collection without any collectibles? Let’s start out by defining a piece of data we want to store:

doc = {
  _key: 'employees',
  firstname: 'Bruce',
  lastname: 'Wayne'

Collection entries (called documents in C8) are plain JavaScript objects and can contain anything you could store in a JSON string. You may be wondering about the _key property: some property names that start with underscores are special in C8 and the key is used to identify the document later. If you don’t specify a key yourself, C8 will generate one for you.

Saving and updating the document

C8 also adds a _rev property which changes every time the document is written to, and an _id which consists of the collection name and document key. These “meta” properties are returned every time you create, update, replace or fetch a document directly.

Let’s see this in action by fist saving the document:


… and then updating it in place:

await collection.update('employees', { email: '' });

Removing the document

We’ve played around enough with this document, so let’s get rid of it:

try {
    await collection.remove('employees');
} catch (e) {

Once the promise has resolved, the document has ceased to exist. We can verify this by trying to fetch it again (which should result in an error).

If you see the error message "document not found", we were successful.


The time has come now to give you a super power. In C8 you don't need to continuously make API calls to see what has changed and when. We have realtime capabilities built in C8. Streams can be local/global.

Stream handle

stream =, false);

Here the last boolean value tells if the stream is local or global. false means that it is global

Create a stream

await stream.createStream();

Subscribing to a stream

Streams have the capability to both consume and produce messages. To create a consumer:

stream.consumer("my-sub", { onmessage:(msg)=>{ console.log(msg) } }, "");

This will create a consumer with a callback of your choice to listen to a stream in realtime.

Publishing to a stream

To publish a message to a stream simply use:

stream.producer("hello world", "");

The first time a producer is created it requires the datacenter name, but not later on.

So now you can simply do:

stream.producer("hey hey hey world");

Note: Remember to close the connections to the stream if you make a consumer or a producer.


Above method will close all the active connection to the stream.

C8QL Queries

const cursor = await fabric.query(c8ql`FOR employee IN employees RETURN employee`);
const result = await;

Note that most queries return a cursor object representing the result set instead of returning an array of all of the results directly.

This helps avoiding unnecessarily cluttering up memory when working with very large result sets.

All interactions with the cursor object are asynchronous as the driver will automatically fetch additional data from the server as necessary. Keep in mind that unlike arrays, cursors are depleted when you use them. They’re single-use items, not permanent data structures.

Template strings

When writing complex queries you don’t want to have to hardcode everything in a giant string. The driver provides the same c8qlQuery template handler you can also use within C8 itself:

c8ql = require('jsc8').c8ql;

You can use it to write c8ql templates. Any variables referenced in c8ql templates will be added to the query’s bind values automatically. It even knows how to treat collection handles.

const cursor = await fabric.query(c8ql`FOR employee IN employees RETURN employee`);
const result = await;

Removing all the documents

Enough fooling around. Let’s end with a clean slate. The method for completely emptying a collection is called “truncate”:

try {
    await collection.truncate();
} catch (e) {

When you truncate a collection, you discard all of its contents. There’s no way back.

Keep in mind that you can also truncate fabrics. Don’t worry about your collections though, truncating only deletes the documents. Although it’s still probably not something you want to take lightly.

Basic usage example

import { Fabric, c8ql } from "jsc8";

const region = "";
const tenantName = "guest";
const fabricName = "fabric1";
const collectionName = "employees";
const streamName = "guest_stream";

// Create a fabric object
const fabric = new Fabric(region);

// Create a guest tenant, guest fabric
const guesttenant = fabric.tenant(tenantName);
await guesttenant.createTenant("my-password");
await fabric.createFabric(fabricName, [{ username: 'root' }], { dcList: region });

// Create and populate employees collection in demofabric
const collection = fabric.collection(collectionName);
await collection.create();
await collection.createHashIndex(['firstname'], true);//Add a hash index to the collection.
await{firstname: 'Jean', lastname: 'Picard'});
await{firstname: 'Bruce', lastname: 'Wayne'});

// Query employees collection
  const cursor = await fabric.query(c8ql`FOR employee IN employees RETURN employee`);
  const result = await;

// Real-time updates from a collection in fabric
  const callback = evt => console.log(evt);
  fabric.onChange(collectionName, callback);

// Create persistent, global and local streams in demofabric
  const persistent_globalStream =, false);
  await persistent_globalStream.createStream();

  const persistent_localStream =, true);
  await persistent_localStream.createStream();

  const streams = await fabric.getStreams();

// Subscribe to a stream
  const stream =, false);
  await stream.createStream();
  stream.consumer("my-sub", { onmessage:(msg)=>{ console.log(msg) } }, region);

// Publish to a stream
  stream.producer("hello world", region);
  stream.producer("hey hey hey world");

// Close all connections to a stream
// or plain old Node-style
var jsC8 = require("jsc8");
var fabric = new jsC8.Fabric();
var stream ="my-stream", true);
  stream.consumer("my-sub", { onmessage:(msg)=>{ console.log(msg) } }, "");
  stream.producer("hello world", "");
var now =;
  query: "RETURN @value",
  bindVars: { value: now }
  .then(function(cursor) {
    return {
      // ...
  .catch(function(err) {
    // ...


Run the tests using the yarn test or npm test commands:

yarn test
# - or -
npm test

To set the environment variable TEST_C8_URL to something different:

TEST_C8_URL= yarn test
# - or -
TEST_C8_URL= npm test


The Apache License, Version 2.0. For more information, see the accompanying LICENSE file.

You can’t perform that action at this time.