DBMS > Amazon Redshift vs. Badger vs. dBASE vs. etcd vs. HEAVY.AI

System Properties Comparison Amazon Redshift vs. Badger vs. dBASE vs. etcd vs. HEAVY.AI

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.

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

A distributed reliable key-value store

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

Primary database model

Secondary database models

Spatial DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.20
Rank	#325	Overall
	#49	Key-value stores

Score	11.18
Rank	#44	Overall
	#28	Relational DBMS

Score	7.64
Rank	#54	Overall
	#5	Key-value stores

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Website

aws.amazon.com/redshift

github.com/dgraph-io/badger

www.dbase.com

etcd.io
github.com/etcd-io/etcd

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

Technical documentation

docs.aws.amazon.com/redshift

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

www.dbase.com/support/knowledgebase

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.heavy.ai

Developer

Amazon (based on PostgreSQL)

DGraph Labs

Asthon Tate

HEAVY.AI, Inc.

Initial release

2012

2017

1979

2016

Current release

dBASE 2019, 2019

3.4, August 2019

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition 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++ and CUDA

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
Windows

experimental

Linux

Data scheme

yes

schema-free

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

none

The IDE can access other DBMS or ODBC-sources.

gRPC
JSON over HTTP

JDBC
ODBC
Thrift
Vega

Supported programming languages

All languages supporting JDBC/ODBC

dBase proprietary IDE

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

user defined functions

in Python

The IDE can access stored procedures in other database systems.

Triggers

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication

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

yes

Transaction concepts

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

ACID

not for dBase internal data, but IDE does support transactions when accessing external DBMS

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.