DBMS > EJDB vs. GeoMesa vs. Newts vs. Sequoiadb vs. Tigris

System Properties Comparison EJDB vs. GeoMesa vs. Newts vs. Sequoiadb vs. Tigris

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.

Time Series DBMS based on Cassandra

NewSQL database with distributed OLTP and SQL

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Document store

Spatial DBMS

Time Series DBMS

Document store
Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

github.com/Softmotions/ejdb

www.geomesa.org

opennms.github.io/newts

www.sequoiadb.com

www.tigrisdata.com

Technical documentation

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

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

github.com/OpenNMS/newts/wiki

www.sequoiadb.com/en/index.php?m=Files&a=index

www.tigrisdata.com/docs

Developer

Softmotions

CCRi and others

OpenNMS Group

Sequoiadb Ltd.

Tigris Data, Inc.

Initial release

2012

2014

2013

2022

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Server: AGPL; Client: Apache V2

Open Source

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

Scala

Java

C++

Server operating systems

server-less

Linux
OS X
Windows

Linux

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

oid, date, timestamp, binary, regex

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

in-process shared library

HTTP REST
Java API

proprietary protocol using JSON

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

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

Java

.Net
C++
Java
PHP
Python

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

selectable replication factor

based on Cassandra

Source-replica replication

yes

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control

Access rights for users and roles

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

Farewell, Froggy: The Age of Ribbit Is Nearing an End
25 May 2013, Mother Jones

provided by Google News

Tigris Data Unveils Beta Launch of New Vector Search Tool
19 May 2023, Datanami

Tigris Data Launches All-in-One Developer Data Platform
27 September 2022, Datanami

FerretDB Provides Alternative to MongoDB
19 May 2023, Datanami

provided by Google News

Share this page