DBMS > GridDB vs. Microsoft Azure Cosmos DB vs. Teradata Aster vs. TimescaleDB vs. Vitess

System Properties Comparison GridDB vs. Microsoft Azure Cosmos DB vs. Teradata Aster vs. TimescaleDB vs. Vitess

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Globally distributed, horizontally scalable, multi-model database service

Platform for big data analytics on multistructured data sources and types

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS

Relational DBMS

Document store
Spatial DBMS

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

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

griddb.net

azure.microsoft.com/services/cosmos-db

www.timescale.com

vitess.io

Technical documentation

docs.griddb.net

learn.microsoft.com/azure/cosmos-db

docs.timescale.com

vitess.io/docs

Developer

Toshiba Corporation

Microsoft

Teradata

Timescale

The Linux Foundation, PlanetScale

Initial release

2013

2014

2005

2017

2013

Current release

5.1, August 2022

2.15.0, May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

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

commercial

Open Source

Apache 2.0

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++

Server operating systems

Linux

hosted

Linux

Linux
OS X
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

JSON types

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

in Aster File Store

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

yes

full PostgreSQL SQL syntax

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C#
C++
Java
Python
R

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

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

JavaScript

R packages

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

yes

proprietary syntax

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Source-replica replication with hot standby and reads on replicas

Multi-source replication
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

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID at container level

Multi-item ACID transactions with snapshot isolation within a partition

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

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

Access rights for users can be defined per database

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.