DBMS > BoltDB vs. DolphinDB vs. GeoMesa vs. GridGain vs. JaguarDB

System Properties Comparison BoltDB vs. DolphinDB vs. GeoMesa vs. GridGain vs. JaguarDB

Editorial information provided by DB-Engines

Name

Description

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

GridGain is an in-memory computing platform, built on Apache Ignite

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Key-value store

Time Series DBMS

Spatial DBMS

Key-value store
Relational DBMS

Key-value store
Vector DBMS

Secondary database models

Relational DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Website

github.com/boltdb/bolt

Technical documentation

docs.dolphindb.cn/en/help200/index.html

www.geomesa.org/documentation/stable/user/index.html

www.gridgain.com/docs/index.html

www.jaguardb.com/support.html

Developer

DolphinDB, Inc

CCRi and others

GridGain Systems, Inc.

DataJaguar, Inc.

Initial release

2013

2018

2014

2007

2015

Current release

v2.00.4, January 2022

5.0.0, May 2024

GridGain 8.5.1

3.3 July 2023

License

Commercial or Open Source

Open Source

MIT License

commercial

free community version available

Open Source

Apache License 2.0

commercial

Open Source

GPL V3.0

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.

Implementation language

C++

Scala

Java, C++, .Net

C++

the server part. Clients available in other languages

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

C#
C++
Java
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

depending on storage layer

yes (replicated cache)

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

depending on storage layer

yes

User concepts

Access control

Administrators, Users, Groups

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

rights management via user accounts

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

What I learnt from building 3 high traffic web applications on an embedded key value store.
21 February 2018, hackernoon.com

4 Instructive Postmortems on Data Downtime and Loss
1 March 2024, The Hacker News

Roblox’s cloud-native catastrophe: A post mortem
31 January 2022, InfoWorld

How to Put a GUI on Ansible, Using Semaphore
22 April 2023, The New Stack

Grafana Loki: Architecture Summary and Running in Kubernetes
14 March 2023, hackernoon.com

provided by Google News

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks and Files

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain: Product Overview and Analysis
5 June 2019, eWeek

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

GridGain, Apache Ignite founder talks in-memory databases
11 August 2022, TechTarget

provided by Google News

Share this page