DBMS > GeoMesa vs. OrientDB vs. Quasardb vs. SQLite vs. TinkerGraph

System Properties Comparison GeoMesa vs. OrientDB vs. Quasardb vs. SQLite vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

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

Multi-model DBMS (Document, Graph, Key/Value)

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

Graph DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

www.orientdb.com/docs/last/index.html

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

CCRi and others

OrientDB LTD; CallidusCloud; SAP

quasardb

Dwayne Richard Hipp

Initial release

2014

2010

2009

2000

2009

Current release

5.0.0, May 2024

3.2.29, March 2024

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2

commercial

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

Open Source

Public Domain

Open Source

Apache 2.0

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

Java

C++

Java

Server operating systems

All OS with a Java JDK (>= JDK 6)

BSD
Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

SQL-like query language, no joins

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

TinkerPop 3

Supported programming languages

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

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Groovy
Java

Server-side scripts

Stored procedures

Java, Javascript

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

none

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using LevelDB

yes

optional

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles; record level security configurable

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.