DBMS > Badger vs. Cubrid vs. FatDB vs. SAP HANA

System Properties Comparison Badger vs. Cubrid vs. FatDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Primary database model

Key-value store

Relational DBMS

Document store
Key-value 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.14
Rank	#328	Overall
	#48	Key-value stores

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/dgraph-io/badger

cubrid.com (korean)
cubrid.org (english)

www.sap.com/products/hana.html

Technical documentation

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

cubrid.org/manuals

help.sap.com/hana

Developer

DGraph Labs

CUBRID Corporation, CUBRID Foundation

FatCloud

SAP

Initial release

2017

2008

2012

2010

Current release

11.0, January 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

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

C, C++, Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Windows

Appliance or cloud-service

Data scheme

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

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

SQLScript, R

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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.