DBMS > EJDB vs. GeoMesa vs. Graph Engine vs. Newts vs. SAP SQL Anywhere

System Properties Comparison EJDB vs. GeoMesa vs. Graph Engine vs. Newts vs. SAP SQL Anywhere

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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Time Series DBMS based on Cassandra

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store

Spatial DBMS

Graph DBMS
Key-value store

Time Series DBMS

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	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

github.com/Softmotions/ejdb

www.geomesa.org

www.graphengine.io

opennms.github.io/newts

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

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

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

www.graphengine.io/docs/manual

github.com/OpenNMS/newts/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Softmotions

CCRi and others

Microsoft

OpenNMS Group

SAP

formerly Sybase

Initial release

2012

2014

2010

2014

1992

Current release

4.0.5, February 2024

17, July 2015

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

Open Source

MIT License

Open Source

Apache 2.0

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

.NET and C

Java

Server operating systems

server-less

.NET

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris
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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

in-process shared library

RESTful HTTP API

HTTP REST
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

C#
C++
F#
Visual Basic

Java

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

Server-side scripts

Stored procedures

yes

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

horizontal partitioning

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

selectable replication factor

based on Cassandra

Source-replica replication

Database mirroring

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

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

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

Trinity
2 June 2023, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

provided by Google News

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

provided by Google News

SAP vulnerabilities Let Attacker Inject OS Commands—Patch Now!
11 July 2023, CybersecurityNews

SAP Again Named a Leader in 2021 Gartner® Magic Quadrant™ for Cloud Database Management Systems
16 December 2021, SAP News

SAP Products & Services Data Portfolio
2 July 2021, Datamation

SAP launches HANA cloud platform, partners with Siemens, Intel
6 May 2015, Channel Daily News

provided by Google News

Share this page