DBMS > Amazon Redshift vs. GridDB vs. Oracle Coherence vs. Sphinx vs. Tigris

System Properties Comparison Amazon Redshift vs. GridDB vs. Oracle Coherence vs. Sphinx vs. Tigris

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Oracles in-memory data grid solution

Open source search engine for searching in data from different sources, e.g. relational databases

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

aws.amazon.com/redshift

griddb.net

www.oracle.com/java/coherence

sphinxsearch.com

www.tigrisdata.com

Technical documentation

docs.aws.amazon.com/redshift

docs.griddb.net

docs.oracle.com/en/middleware/standalone/coherence

sphinxsearch.com/docs

www.tigrisdata.com/docs

Developer

Amazon (based on PostgreSQL)

Toshiba Corporation

Oracle

Sphinx Technologies Inc.

Tigris Data, Inc.

Initial release

2012

2013

2007

2001

2022

Current release

5.1, August 2022

14.1, August 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

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

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache Version 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

C++

Java

C++

Server operating systems

hosted

Linux

All OS with a Java VM

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JCache
JPA
RESTful HTTP API

Proprietary protocol

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C++
Java

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes, with selectable consistency level

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Immediate consistency within container, eventual consistency across containers

Eventual Consistency
Immediate Consistency

Immediate 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

ACID at container level

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

yes

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

yes, using FoundationDB

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

Access rights for users can be defined per database

authentification to access the cache via certificates or http basic authentication

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.