DBMS > EJDB vs. Google BigQuery vs. Manticore Search vs. Newts vs. Rockset

System Properties Comparison EJDB vs. Google BigQuery vs. Manticore Search vs. Newts vs. Rockset

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Large scale data warehouse service with append-only tables

Multi-storage database for search, including full-text search.

Time Series DBMS based on Cassandra

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Relational DBMS
Search engine

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.23
Rank	#317	Overall
	#21	Search engines

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	0.84
Rank	#209	Overall
	#35	Document stores

Website

github.com/Softmotions/ejdb

cloud.google.com/bigquery

manticoresearch.com

opennms.github.io/newts

rockset.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigquery/docs

manual.manticoresearch.com

github.com/OpenNMS/newts/wiki

docs.rockset.com

Developer

Softmotions

Google

Manticore Software

OpenNMS Group

Rockset

Initial release

2012

2010

2017

2014

2019

Current release

6.0, February 2023

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

GPL version 2

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

C++

Server operating systems

server-less

hosted

FreeBSD
Linux
macOS
Windows

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

dynamic typing

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Can index from XML

ingestion from XML files supported

Secondary indexes

yes

full-text index on all search fields

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

Read-only SQL queries, including JOINs

APIs and other access methods

in-process shared library

RESTful HTTP/JSON API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

HTTP REST
Java API

HTTP REST

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Java

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on Cassandra

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Since BigQuery is designed for querying data

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users and organizations can be defined via Rockset console

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.