DBMS > GeoMesa vs. JanusGraph vs. MySQL vs. Quasardb

System Properties Comparison GeoMesa vs. JanusGraph vs. MySQL vs. Quasardb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Widely used open source RDBMS

Distributed, high-performance timeseries database

Primary database model

Spatial DBMS

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

Technical documentation

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

docs.janusgraph.org

dev.mysql.com/doc

doc.quasar.ai/master

Developer

CCRi and others

Linux Foundation; originally developed as Titan by Aurelius

Oracle

since 2010, originally MySQL AB, then Sun

quasardb

Initial release

2014

2017

1995

2009

Current release

5.0.0, May 2024

0.6.3, February 2023

8.4.0, April 2024

3.14.1, January 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

Java

C and C++

C++

Server operating systems

Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

Clojure
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

by using LevelDB

In-memory capabilities

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

depending on storage layer

yes

Transient mode

User concepts

Access control

yes

depending on the DBMS used for storage

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept

no user groups or roles

Cryptographically strong user authentication and audit trail

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.