DBMS > Amazon Redshift vs. CockroachDB vs. Manticore Search vs. RDF4J

System Properties Comparison Amazon Redshift vs. CockroachDB vs. Manticore Search vs. RDF4J

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Relational DBMS

Search engine

RDF store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Website

aws.amazon.com/redshift

www.cockroachlabs.com

manticoresearch.com

rdf4j.org

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

manual.manticoresearch.com

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

Cockroach Labs

Manticore Software

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2012

2015

2017

2004

Current release

24.1.0, May 2024

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

GPL version 2

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Server operating systems

hosted

Linux
macOS
Windows

FreeBSD
Linux
macOS
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

dynamic schema

Fixed schema

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

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

yes

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

Secondary indexes

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, wire compatible with PostgreSQL

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

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

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

Synchronous replication based on Galera library

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

in-memory storage is supported as well

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

Role-based access control

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.