DBMS > Amazon Redshift vs. KeyDB vs. LeanXcale vs. Oracle Berkeley DB

System Properties Comparison Amazon Redshift vs. KeyDB vs. LeanXcale vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Widely used in-process key-value store

Primary database model

Relational DBMS

Key-value store

Key-value store
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

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

Score	0.36
Rank	#280	Overall
	#40	Key-value stores
	#129	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Website

aws.amazon.com/redshift

github.com/Snapchat/KeyDB
keydb.dev

www.leanxcale.com

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

docs.aws.amazon.com/redshift

docs.keydb.dev

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Amazon (based on PostgreSQL)

EQ Alpha Technology Ltd.

LeanXcale

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2019

2015

1994

Current release

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

Open Source

commercial license available

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++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-free

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

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

through Apache Derby

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

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

C
Java
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

Concurrency

Support for concurrent manipulation of data

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

simple password-based access control and ACL

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.