DBMS > Amazon Redshift vs. Dolt vs. Graphite vs. GridDB

System Properties Comparison Amazon Redshift vs. Dolt vs. Graphite vs. GridDB

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

A MySQL compatible DBMS with Git-like versioning of data and schema

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store

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.93
Rank	#194	Overall
	#90	Relational DBMS

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/dolthub/dolt
www.dolthub.com

github.com/graphite-project/graphite-web

griddb.net

Technical documentation

docs.aws.amazon.com/redshift

docs.dolthub.com

graphite.readthedocs.io

docs.griddb.net

Developer

Amazon (based on PostgreSQL)

DoltHub Inc

Chris Davis

Toshiba Corporation

Initial release

2012

2018

2006

2013

Current release

5.1, August 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also 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

Python

C++

Server operating systems

hosted

Linux
macOS
Windows

Linux
Unix

Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

yes

numerical, string, blob, geometry, boolean, timestamp

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

yes

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

JDBC
ODBC

CLI Client
HTTP REST

HTTP API
Sockets

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

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

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

currently in alpha release

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

none

Source-replica replication

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

none

Immediate consistency within container, eventual consistency across containers

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

ACID at container level

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

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

Only one user is configurable, and must be specified in the config file at startup

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.