DBMS > EJDB vs. GeoMesa vs. Microsoft Azure Table Storage vs. Newts vs. Sequoiadb

System Properties Comparison EJDB vs. GeoMesa vs. Microsoft Azure Table Storage vs. Newts vs. Sequoiadb

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.

A Wide Column Store for rapid development using massive semi-structured datasets

Time Series DBMS based on Cassandra

NewSQL database with distributed OLTP and SQL

Primary database model

Document store
Relational 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	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Website

github.com/Softmotions/ejdb

www.geomesa.org

azure.microsoft.com/en-us/services/storage/tables

opennms.github.io/newts

www.sequoiadb.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

Developer

Softmotions

CCRi and others

Microsoft

OpenNMS Group

Sequoiadb Ltd.

Initial release

2012

2014

2012

2014

2013

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

Open Source

Server: AGPL; Client: Apache V2

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

Scala

Java

C++

Server operating systems

server-less

hosted

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

oid, date, timestamp, binary, regex

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

RESTful HTTP API

HTTP REST
Java API

proprietary protocol using JSON

Supported programming languages

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

selectable replication factor

based on Cassandra

Source-replica replication

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual 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

optimistic locking

Document is locked during a transaction

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

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights based on private key authentication or shared access signatures

simple password-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

Working with Azure to Use and Manage Data Lakes
7 March 2024, Simplilearn

Azure Cosmos DB Data Migration tool imports from Azure Table storage | Azure updates
5 May 2015, Microsoft

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

How to use Azure Table storage in .Net
14 January 2019, InfoWorld

Quick Guide to Azure Storage Pricing
16 May 2023, DevOps.com

provided by Google News

Share this page