DBMS > EJDB vs. GeoMesa vs. Graphite vs. Oracle NoSQL

System Properties Comparison EJDB vs. GeoMesa vs. Graphite 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.

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

Time Series DBMS

Document store
Key-value 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.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

github.com/Softmotions/ejdb

www.geomesa.org

github.com/graphite-project/graphite-web

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

graphite.readthedocs.io

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

Developer

Softmotions

CCRi and others

Chris Davis

Oracle

Initial release

2012

2014

2006

2011

Current release

4.0.5, February 2024

23.3, December 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Python

Java

Server operating systems

server-less

Linux
Unix

Linux
Solaris SPARC/x86

Data scheme

schema-free

yes

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

Numeric data only

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

HTTP API
Sockets

RESTful HTTP API

Supported programming languages

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

JavaScript (Node.js)
Python

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

none

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

none

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

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

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

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, Paul Andlinger

show all

Recent citations in the news

Try out the Graphite monitoring tool for time-series data
29 October 2019, TechTarget

Grafana Labs Announces Mimir Time Series Database
1 April 2022, Datanami

The Billion Data Point Challenge: Building a Query Engine for High Cardinality Time Series Data
10 December 2018, Uber

Getting Started with Monitoring using Graphite
23 January 2015, InfoQ.com

The value of time series data and TSDBs
10 June 2021, InfoWorld

provided by Google News

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

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

Database Technologies
4 September 2018, oracle.com

Oracle Defends Relational DBs Against NoSQL Competitors
25 November 2015, eWeek

Oracle Adds New AI-Enabling Features To MySQL HeatWave
23 March 2023, Forbes

provided by Google News

Share this page