DBMS > EJDB vs. GeoMesa vs. Microsoft Azure Table Storage vs. Oracle NoSQL

System Properties Comparison EJDB vs. GeoMesa vs. Microsoft Azure Table Storage vs. Oracle NoSQL

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.

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Document store

Spatial DBMS

Wide column store

Document store
Key-value store
Relational DBMS

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	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Website

github.com/Softmotions/ejdb

www.geomesa.org

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

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

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

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

Softmotions

CCRi and others

Microsoft

Oracle

Initial release

2012

2014

2012

2011

Current release

5.0.0, May 2024

24.1, May 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Server operating systems

server-less

hosted

Linux
Solaris SPARC/x86

Data scheme

schema-free

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

optional

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 DML and DDL statements

APIs and other access methods

in-process shared library

RESTful HTTP API

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

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Implicit feature of the cloud service

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.

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights based on private key authentication or shared access signatures

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

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

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

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

provided by Google News

Oracle Beefs Up Its NoSQL Database Offering
31 May 2024, Data Center Knowledge

OpenWorld 2013: Oracle NoSQL Database On the Rise?
13 December 2023, Channel Futures

Blog Theme - Details
21 August 2023, blogs.oracle.com

We built a geo-distributed, serverless modern app using the Oracle NoSQL Database Cloud Service
18 November 2021, blogs.oracle.com

Oracle NoSQL database comes to the cloud
2 April 2020, TechTarget

provided by Google News

Share this page