DBMS > BoltDB vs. Ehcache vs. etcd vs. Google BigQuery vs. Hazelcast

System Properties Comparison BoltDB vs. Ehcache vs. etcd vs. Google BigQuery vs. Hazelcast

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A widely adopted Java cache with tiered storage options

A distributed reliable key-value store

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Primary database model

Key-value store

Relational DBMS

Key-value store

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.74
Rank	#220	Overall
	#31	Key-value stores

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Website

github.com/boltdb/bolt

www.ehcache.org

etcd.io
github.com/etcd-io/etcd

cloud.google.com/bigquery

hazelcast.com

Technical documentation

www.ehcache.org/documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

Developer

Terracotta Inc, owned by Software AG

Google

Hazelcast

Initial release

2013

2009

2010

2008

Current release

3.10.0, March 2022

3.4, August 2019

5.3.6, November 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2; commercial licenses available

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

All OS with a Java VM

FreeBSD
Linux
Windows

experimental

hosted

All OS with a Java VM

Data scheme

schema-free

yes

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JCache

gRPC
JSON over HTTP

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

Java

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

Triggers

yes

Cache Event Listeners

yes, watching key changes

yes

Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

Replicated Map

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

Transaction concepts

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

yes

supports JTA and can work as an XA resource

Since BigQuery is designed for querying data

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & 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.