DBMS > Amazon Redshift vs. Hazelcast vs. SQLite vs. TerminusDB vs. Transbase

System Properties Comparison Amazon Redshift vs. Hazelcast vs. SQLite vs. TerminusDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted in-memory data grid

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

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

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
RDF store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

aws.amazon.com/redshift

hazelcast.com

www.sqlite.org

terminusdb.com

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

Technical documentation

docs.aws.amazon.com/redshift

hazelcast.org/imdg/docs

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

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

Developer

Amazon (based on PostgreSQL)

Hazelcast

Dwayne Richard Hipp

DataChemist Ltd.

Transaction Software GmbH

Initial release

2012

2008

2000

2018

1987

Current release

5.3.6, November 2023

3.46.1 (13 August 2024), August 2024

11.0.0, January 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

Open Source

GPL V3

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

Java

Prolog, Rust

C and C++

Server operating systems

hosted

All OS with a Java VM

server-less

Linux

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

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

the object must implement a serialization strategy

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

yes

APIs and other access methods

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

JavaScript
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

none

Journaling Streams

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Role-based access control

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.