DBMS > Citus vs. GBase vs. Ignite vs. Snowflake vs. Tkrzw

System Properties Comparison Citus vs. GBase vs. Ignite vs. Snowflake vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Key-value store

Secondary database models

Document store

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

Technical documentation

docs.citusdata.com

apacheignite.readme.io/docs

docs.snowflake.net/manuals/index.html

Developer

General Data Technology Co., Ltd.

Apache Software Foundation

Snowflake Computing Inc.

Mikio Hirabayashi

Initial release

2010

2004

2015

2014

2020

Current release

8.1, December 2018

GBase 8a, GBase 8s, GBase 8c

Apache Ignite 2.6

0.9.3, August 2020

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

Open Source

Apache 2.0

commercial

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, Python

C++, Java, .Net

C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

hosted

Linux
macOS

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

Standard with numerous extensions

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

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

ADO.NET
C API
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes

yes (replicated cache)

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

Security Hooks for custom implementations

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

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.