DBMS > Badger vs. Dolt vs. HEAVY.AI vs. Oracle

System Properties Comparison Badger vs. Dolt vs. HEAVY.AI vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A MySQL compatible DBMS with Git-like versioning of data and schema

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

Widely used RDBMS

Primary database model

Key-value store

Relational DBMS

Secondary database models

Document store

Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.14
Rank	#328	Overall
	#48	Key-value stores

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Website

github.com/dgraph-io/badger

github.com/dolthub/dolt
www.dolthub.com

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

www.oracle.com/database

Technical documentation

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

docs.dolthub.com

docs.heavy.ai

docs.oracle.com/en/database

Developer

DGraph Labs

DoltHub Inc

HEAVY.AI, Inc.

Oracle

Initial release

2017

2018

2016

1980

Current release

5.10, January 2022

23c, September 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++ and CUDA

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

CLI Client
HTTP REST

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

currently in alpha release

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

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.