DBMS > Blazegraph vs. ClickHouse vs. Elasticsearch vs. Geode vs. Oracle Berkeley DB

System Properties Comparison Blazegraph vs. ClickHouse vs. Elasticsearch vs. Geode vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Time Series DBMS

Document store
Spatial DBMS
Vector DBMS

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

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

Website

blazegraph.com

clickhouse.com

www.elastic.co/elasticsearch

geode.apache.org

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

Technical documentation

wiki.blazegraph.com

clickhouse.com/docs

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

geode.apache.org/docs

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

Developer

Blazegraph

Clickhouse Inc.

Elastic

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2006

2016

2010

2002

1994

Current release

2.1.5, March 2019

v24.4.1.2088-stable, May 2024

8.6, January 2023

1.1, February 2017

18.1.40, May 2020

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

Apache 2.0

Open Source

Elastic License

Open Source

Apache Version 2; commercial licenses available as Gemfire

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

Java

C++

Java

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

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

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

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SPARQL is used as query language

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language

SQL-like query language (OQL)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

Java API
RESTful HTTP/JSON API

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

.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

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

Cache Event Listeners

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

yes

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

Transaction concepts

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

ACID

yes, on a single node

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

Memcached and Redis integration

yes

User concepts

Access control

Security and Authentication via Web Application Container (Tomcat, Jetty)

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights per client and object definable

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.