DBMS > Amazon Redshift vs. GigaSpaces vs. GridDB vs. XTDB

System Properties Comparison Amazon Redshift vs. GigaSpaces vs. GridDB vs. XTDB

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Scalable in-memory time series database optimized for IoT and Big Data

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Time Series DBMS

Document store

Secondary database models

Graph DBMS
Search engine

Key-value store
Relational DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.91
Rank	#197	Overall
	#33	Document stores
	#7	Object oriented DBMS

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

aws.amazon.com/redshift

www.gigaspaces.com

griddb.net

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.gigaspaces.com/latest/landing.html

docs.griddb.net

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Gigaspaces Technologies

Toshiba Corporation

Juxt Ltd.

Initial release

2012

2000

2013

2019

Current release

15.5, September 2020

5.1, August 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

MIT License

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++, .Net

C++

Clojure

Server operating systems

hosted

Linux
macOS
Solaris
Windows

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes, extensible-data-notation format

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.

XML can be used for describing objects metadata

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-99 for query and DML statements

SQL92, SQL-like TQL (Toshiba Query Language)

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C++
Java
Python
Scala

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate consistency within container, eventual consistency across containers

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

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Access rights for users can be defined per database

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.