DBMS > Badger vs. Dgraph vs. Google Cloud Bigtable vs. Hazelcast vs. SQLite

System Properties Comparison Badger vs. Dgraph vs. Google Cloud Bigtable vs. Hazelcast vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

Distributed and scalable native Graph DBMS

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A widely adopted in-memory data grid

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Graph DBMS

Key-value store
Wide column store

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/dgraph-io/badger

dgraph.io

cloud.google.com/bigtable

hazelcast.com

www.sqlite.org

Technical documentation

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

dgraph.io/docs

cloud.google.com/bigtable/docs

hazelcast.org/imdg/docs

www.sqlite.org/docs.html

Developer

DGraph Labs

Dgraph Labs, Inc.

Google

Hazelcast

Dwayne Richard Hipp

Initial release

2017

2016

2015

2008

2000

Current release

5.3.6, November 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

hosted

All OS with a Java VM

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication via Raft

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

Replicated Map

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Planned for future releases

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Role-based access control

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.