DBMS > Amazon Redshift vs. Badger vs. HEAVY.AI vs. Realm

System Properties Comparison Amazon Redshift vs. Badger vs. HEAVY.AI vs. Realm

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 embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Secondary database models

Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Website

aws.amazon.com/redshift

github.com/dgraph-io/badger

github.com/heavyai/heavydb
www.heavy.ai

realm.io

Technical documentation

docs.aws.amazon.com/redshift

godoc.org/github.com/dgraph-io/badger

docs.heavy.ai

realm.io/docs

Developer

Amazon (based on PostgreSQL)

DGraph Labs

HEAVY.AI, Inc.

Realm, acquired by MongoDB in May 2019

Initial release

2012

2017

2016

2014

Current release

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2; enterprise edition available

Open Source

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

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Linux

Android
Backend: server-less
iOS
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/Thrift
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

user defined functions

in Python

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

yes

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.