DBMS > BigObject vs. Dolt vs. GeoMesa vs. Hazelcast

System Properties Comparison BigObject vs. Dolt vs. GeoMesa vs. Hazelcast

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A MySQL compatible DBMS with Git-like versioning of data and schema

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

A widely adopted in-memory data grid

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Spatial 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.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

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

Website

bigobject.io

github.com/dolthub/dolt
www.dolthub.com

www.geomesa.org

hazelcast.com

Technical documentation

docs.bigobject.io

docs.dolthub.com

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

hazelcast.org/imdg/docs

Developer

BigObject, Inc.

DoltHub Inc

CCRi and others

Hazelcast

Initial release

2015

2018

2014

2008

Current release

4.0.5, February 2024

5.3.6, November 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses 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.

Implementation language

Scala

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
macOS
Windows

All OS with a Java VM

Data scheme

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

SQL-like DML and DDL statements

yes

SQL-like query language

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

CLI Client
HTTP REST

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

Lua

yes

currently in alpha release

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

depending on storage layer

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

depending on storage layer

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

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

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

Only one user is configurable, and must be specified in the config file at startup

yes

depending on the DBMS used for storage

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.

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

Dolt- A Version Controlled Database
29 January 2024, iProgrammer

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

Are you still not using Version Control for Data?
11 April 2020, Towards Data Science

provided by Google News

Hazelcast Showcases Real-Time Data Platform at 2024 Gartner Summit
15 May 2024, Datanami

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Real-Time Data Platform Hazelcast Introduces New Chief Technology Officer Adrian Soars
7 November 2023, Finovate

Hazelcast to Demonstrate Power of Unified Platform for Real-Time and AI Applications at the ...
13 May 2024, WDRB

provided by Google News

Share this page