MonsterDB – Documentation

monsterDB - documentation

Server Commands

Connect to, and disconnect from servers, create, list and and drop databases .

Database Commands

A monsterDB database stores many collections, each database acts independently and does not see the contents of other databases. If you drop a a database it will drop all the collections within it. Collections in MonsterDB take two distinct forms, but they act very similar to each other, there are normal collections and fuzzy collections.

Collection Commands

Briefly a collection stores one or many documents, these documents are in monsterDB JSON format, which is the same as a standard JSON document but can also store additional tagged objects such as images, document references and identifiers. To use the following Commands you must have created a collection to work with. Collections are independent, but they can store document references to documents in other collections.

Pipeline Stages

Pipelines allow us to chain together monsterDB commands to create various process that are executed by the optimiser or fuzzy matching system. the pipeline consists of a set of statements in a list and can be executed either at the Command Line (CLI) or via the API


Operators allow you to specify the behaviour of the system, like using logical statements (or, and) expressions are multiple function type statements built up in a document structure.

Loading Data

Data can currently be loaded into monsterDB in one of three ways, using a standard insert/save command either from the API or the Command Line interface, using the bulk saveMany command that will effectively perform an “upsert” into the collection or using the loadFile command, an alternate loadJDBC method is currently under construction.