DBMS > Amazon Redshift vs. GBase vs. KeyDB vs. SQLite vs. Transbase

System Properties Comparison Amazon Redshift vs. GBase vs. KeyDB vs. SQLite vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Widely used embeddable, in-process RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/redshift

www.gbase.cn

github.com/Snapchat/KeyDB
keydb.dev

www.sqlite.org

www.transaction.de/en/products/transbase.html

Technical documentation

docs.aws.amazon.com/redshift

docs.keydb.dev

www.sqlite.org/docs.html

www.transaction.de/en/products/transbase/features.html

Developer

Amazon (based on PostgreSQL)

General Data Technology Co., Ltd.

EQ Alpha Technology Ltd.

Dwayne Richard Hipp

Transaction Software GmbH

Initial release

2012

2004

2019

2000

1987

Current release

GBase 8a, GBase 8s, GBase 8c

3.46.0 (23 May 2024), May 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

Public Domain

commercial

free development 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, Java, Python

C++

C and C++

Server operating systems

hosted

Linux

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

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

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

restricted

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Standard with numerous extensions

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
C API
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

fine grained access rights according to SQL-standard

yes

simple password-based access control and ACL

fine grained access rights according to SQL-standard

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.