DBMS > Amazon Redshift vs. BigObject vs. Ehcache vs. TigerGraph vs. TinkerGraph

System Properties Comparison Amazon Redshift vs. BigObject vs. Ehcache vs. TigerGraph vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

A widely adopted Java cache with tiered storage options

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Graph DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

aws.amazon.com/redshift

bigobject.io

www.ehcache.org

www.tigergraph.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

www.ehcache.org/documentation

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Terracotta Inc, owned by Software AG

Initial release

2012

2015

2009

2017

2009

Current release

3.10.0, March 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.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

Java

C++

Java

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

JCache

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC

Java

C++
Java

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

by using Terracotta Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Tunable Consistency (Strong, Eventual, Weak)

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

Relationships in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

optional

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.