DBMS > GridGain vs. Kingbase vs. Redis vs. TerarkDB

System Properties Comparison GridGain vs. Kingbase vs. Redis vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Key-value store

Secondary database models

Document store
Spatial DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.44
Rank	#258	Overall
	#117	Relational DBMS

Score	149.43
Rank	#6	Overall
	#1	Key-value stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

www.gridgain.com

www.kingbase.com.cn

redis.com
redis.io

github.com/bytedance/terarkdb

Technical documentation

www.gridgain.com/docs/index.html

docs.redis.com/latest/index.html
redis.io/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

GridGain Systems, Inc.

BeiJing KINGBASE Information technologies inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

ByteDance, originally Terark

Initial release

2007

1999

2009

2016

Current release

GridGain 8.5.1

V8.0, August 2021

7.2.5, May 2024

License

Commercial or Open Source

commercial, open source

commercial

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, C++, .Net, Python, REST, SQL

C and Java

C++

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

with RediSearch module

SQL

Support of SQL

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

Standard with numerous extensions

with RediSQL module

APIs and other access methods

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

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

proprietary protocol

RESP - REdis Serialization Protocol

C++ API
Java API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C++
Java

Server-side scripts

Stored procedures

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

user defined functions

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

yes (cache interceptors and events)

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Role-based access control
Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based 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.