DBMS > Amazon Redshift vs. EJDB vs. Manticore Search vs. Newts vs. Rockset

System Properties Comparison Amazon Redshift vs. EJDB vs. Manticore Search vs. Newts vs. Rockset

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

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	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.30
Rank	#294	Overall
	#44	Document stores

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

aws.amazon.com/redshift

github.com/Softmotions/ejdb

manticoresearch.com

opennms.github.io/newts

rockset.com

Technical documentation

docs.aws.amazon.com/redshift

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

manual.manticoresearch.com

github.com/OpenNMS/newts/wiki

docs.rockset.com

Developer

Amazon (based on PostgreSQL)

Softmotions

Manticore Software

OpenNMS Group

Rockset

Initial release

2012

2017

2014

2019

Current release

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

GPLv2

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

hosted

server-less

FreeBSD
Linux
macOS
Windows

Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

restricted

yes

full-text index on all search fields

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
ODBC

in-process shared library

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

HTTP REST
Java API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
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 Python

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

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

yes

informational only, not enforced by the system

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.