DBMS > Cassandra vs. Dgraph vs. Hawkular Metrics vs. Oracle Berkeley DB

System Properties Comparison Cassandra vs. Dgraph vs. Hawkular Metrics vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Distributed and scalable native Graph DBMS

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Widely used in-process key-value store

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Vector DBMS

starting with release V5

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

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

cassandra.apache.org

dgraph.io

www.hawkular.org

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

cassandra.apache.org/doc/latest

dgraph.io/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Dgraph Labs, Inc.

Community supported by Red Hat

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2008

2016

2014

1994

Current release

4.1.3, July 2023

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

commercial license 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.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

BSD
Linux
OS X
Windows

Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

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

only with the Berkeley DB XML edition

Secondary indexes

restricted

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

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

HTTP REST

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

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

Go
Java
Python
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

Triggers

yes

via Hawkular Alerting

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

Synchronous replication via Raft

selectable replication factor

based on Cassandra

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

Transaction concepts

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

Atomicity and isolation are supported for single operations

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

Access rights for users can be defined per object

Planned for future releases

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

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.