DBMS > BoltDB vs. Hazelcast vs. Kyligence Enterprise vs. Microsoft Azure Cosmos DB

System Properties Comparison BoltDB vs. Hazelcast vs. Kyligence Enterprise vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A widely adopted in-memory data grid

A distributed analytics engine for big data, built on top of Apache Kylin

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	0.70
Rank	#225	Overall
	#31	Key-value stores

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	0.44
Rank	#259	Overall
	#118	Relational DBMS

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

github.com/boltdb/bolt

hazelcast.com

kyligence.io/kyligence-enterprise

azure.microsoft.com/services/cosmos-db

Technical documentation

hazelcast.org/imdg/docs

learn.microsoft.com/azure/cosmos-db

Developer

Hazelcast

Kyligence, Inc.

Microsoft

Initial release

2013

2008

2016

2014

Current release

5.3.6, November 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

commercial

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

Linux

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

ANSI SQL for queries (using Apache Calcite)

SQL-like query language

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

Triggers

yes

Events

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

Multi-item ACID transactions with snapshot isolation within a partition

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

Role-based access control

Access rights can be defined down to the item level

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.