DBMS > Badger vs. IBM Cloudant vs. SAP HANA vs. Spark SQL

System Properties Comparison Badger vs. IBM Cloudant vs. SAP HANA vs. Spark SQL

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.

Database as a Service offering based on Apache CouchDB

In-memory, column based data store. Available as appliance or cloud service

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Key-value store

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

github.com/dgraph-io/badger

www.ibm.com/products/cloudant

www.sap.com/products/hana.html

spark.apache.org/sql

Technical documentation

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

cloud.ibm.com/docs/Cloudant

help.sap.com/hana

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

DGraph Labs

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SAP

Apache Software Foundation

Initial release

2017

2010

2014

Current release

2.0 SPS07 (April 4, 2023), April 2023

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

Scala

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

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

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

Java
Python
R
Scala

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

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.