DBMS > GridDB vs. PostGIS vs. Snowflake vs. TimescaleDB vs. XTDB

System Properties Comparison GridDB vs. PostGIS vs. Snowflake vs. TimescaleDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of PostgreSQL

Cloud-based data warehousing service for structured and semi-structured data

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

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

Primary database model

Secondary database models

Key-value store
Relational DBMS

Relational DBMS

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

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

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

Technical documentation

docs.griddb.net

postgis.net/documentation

docs.snowflake.net/manuals/index.html

docs.timescale.com

www.xtdb.com/docs

Developer

Toshiba Corporation

Snowflake Computing Inc.

Timescale

Juxt Ltd.

Initial release

2013

2005

2014

2017

2019

Current release

5.1, August 2022

3.4.2, February 2024

2.15.0, May 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

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

Open Source

GPL v2.0

commercial

Open Source

Apache 2.0

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

C++

Clojure

Server operating systems

Linux

hosted

Linux
OS X
Windows

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

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

full PostgreSQL SQL syntax

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

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

HTTP REST
JDBC

Supported programming languages

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

JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

yes

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

based on PostgreSQL

yes

Source-replica replication with hot standby and reads on replicas

yes, each node contains all data

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 within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

Access rights for users can be defined per database

yes

based on PostgreSQL

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.