DBMS > Amazon Redshift vs. Graph Engine vs. Hypertable vs. Solr vs. TerarkDB

System Properties Comparison Amazon Redshift vs. Graph Engine vs. Hypertable vs. Solr vs. TerarkDB

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

An open source BigTable implementation based on distributed file systems such as Hadoop

A widely used distributed, scalable search engine based on Apache Lucene

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Wide column store

Search engine

Key-value store

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

www.graphengine.io

solr.apache.org

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

solr.apache.org/resources.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Microsoft

Hypertable Inc.

Apache Software Foundation

ByteDance, originally Terark

Initial release

2012

2010

2009

2006

2016

Current release

0.9.8.11, March 2016

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

GNU version 3. Commercial license available

Open Source

Apache Version 2

commercial

restricted open source version available

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

.NET and C

C++

Java

C++

Server operating systems

hosted

.NET

Linux
OS X
Windows

an inofficial Windows port is available

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic 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.

yes

Secondary indexes

restricted

only exact value or prefix value scans

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

C++ API
Thrift

Java API
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

C++
Java
Perl
PHP
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor on file system level

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

yes

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.