DBMS > Amazon Redshift vs. Ehcache vs. SQLite vs. TinkerGraph vs. Transbase

System Properties Comparison Amazon Redshift vs. Ehcache vs. SQLite vs. TinkerGraph vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted Java cache with tiered storage options

Widely used embeddable, in-process RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

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

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/redshift

www.ehcache.org

www.sqlite.org

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

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

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

www.sqlite.org/docs.html

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

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Dwayne Richard Hipp

Transaction Software GmbH

Initial release

2012

2009

2000

2009

1987

Current release

3.10.0, March 2022

3.46.0 (23 May 2024), May 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

Open Source

Apache 2.0

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

C and C++

Server operating systems

hosted

All OS with a Java VM

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC
ODBC

JCache

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

TinkerPop 3

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

Java

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

Groovy
Java

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

optional

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

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.