DBMS > EJDB vs. GeoMesa vs. HBase vs. InfinityDB

System Properties Comparison EJDB vs. GeoMesa vs. HBase vs. InfinityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

A Java embedded Key-Value Store which extends the Java Map interface

Primary database model

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Website

github.com/Softmotions/ejdb

www.geomesa.org

hbase.apache.org

boilerbay.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

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

hbase.apache.org/book.html

boilerbay.com/infinitydb/manual

Developer

Softmotions

CCRi and others

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Boiler Bay Inc.

Initial release

2012

2014

2008

2002

Current release

5.0.0, May 2024

2.3.4, January 2021

4.0

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

Open Source

Apache version 2

commercial

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

server-less

Linux
Unix
Windows

using Cygwin

All OS with a Java VM

Data scheme

schema-free

yes

schema-free, schema definition possible

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

options to bring your own types, AVRO

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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.

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

APIs and other access methods

in-process shared library

Java API
RESTful HTTP API
Thrift

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

Java

Server-side scripts

Stored procedures

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency or Eventual Consistency

Immediate Consistency

READ-COMMITTED or SERIALIZED

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

Optimistic locking for transactions; no isolation for bulk loads

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

Why is Hadoop not listed in the DB-Engines Ranking?
13 May 2013, Paul Andlinger

show all

Recent citations in the news

Less Components, Higher Performance: Apache Doris instead of ClickHouse, MySQL, Presto, and HBase
20 October 2023, hackernoon.com

What Is HBase?
19 August 2021, IBM

HBase: The database big data left behind
6 May 2016, InfoWorld

Monitor Apache HBase on Amazon EMR using Amazon Managed Service for Prometheus and Amazon Managed ...
13 February 2023, AWS Blog

HydraBase – The evolution of HBase@Facebook
5 June 2014, Facebook Engineering

provided by Google News

Share this page