DBMS > Amazon Redshift vs. eXtremeDB vs. TigerGraph vs. Vitess

System Properties Comparison Amazon Redshift vs. eXtremeDB vs. TigerGraph vs. Vitess

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

Natively in-memory DBMS with options for persistency, high-availability and clustering

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.80
Rank	#214	Overall
	#99	Relational DBMS
	#18	Time Series DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

aws.amazon.com/redshift

www.mcobject.com

www.tigergraph.com

vitess.io

Technical documentation

docs.aws.amazon.com/redshift

www.mcobject.com/docs/extremedb.htm

docs.tigergraph.com

vitess.io/docs

Developer

Amazon (based on PostgreSQL)

McObject

The Linux Foundation, PlanetScale

Initial release

2012

2001

2017

2013

Current release

8.2, 2021

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses 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

C and C++

C++

Server operating systems

hosted

AIX
HP-UX
Linux
macOS
Solaris
Windows

Linux

Docker
Linux
macOS

Data scheme

yes

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.

support of XML interfaces available

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with the option: eXtremeSQL

SQL-like query language (GSQL)

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
Java
Lua
Python
Scala

C++
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

proprietary syntax

Triggers

yes

by defining events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning / sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

eXtremeDB is an in-memory and/or persistent database system that offers an ultra-small...
» more

Competitive advantages

eXtremeDB databases can be modeled relationally or as objects and can utilize SQL...
» more

Typical application scenarios

IoT application across all markets: Industrial Control, Netcom, Telecom, Defense,...
» more

Key customers

Schneider Electronics, F5 Networks, TNS, Boeing, Northrop Grumman, GoPro, ViaSat,...
» more

Market metrics

With hundreds of customers and over 30 million devices/applications using the product...
» more

Licensing and pricing models

For server use cases, there is a simple per-server license irrespective of the number...
» more

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.