DBMS > GeoMesa vs. OrientDB vs. Stardog vs. Valentina Server

System Properties Comparison GeoMesa vs. OrientDB vs. Stardog vs. Valentina Server

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.

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Object-relational database and reports server

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store

Graph DBMS
RDF store

Relational DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	3.02
Rank	#88	Overall
	#16	Document stores
	#6	Graph DBMS
	#12	Key-value stores

Score	1.93
Rank	#121	Overall
	#10	Graph DBMS
	#6	RDF stores

Score	0.18
Rank	#313	Overall
	#140	Relational DBMS

Website

Technical documentation

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

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

docs.stardog.com

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

CCRi and others

OrientDB LTD; CallidusCloud; SAP

Stardog-Union

Paradigma Software

Initial release

2014

2010

1999

Current release

5.0.1, July 2024

3.2.29, March 2024

7.3.0, May 2020

5.7.5

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Java

Server operating systems

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

Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

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

schema-free and OWL/RDFS-schema support

yes

Typing

predefined data types such as float or date

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

SQL-like query language, no joins

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

yes

APIs and other access methods

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

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

ODBC

Supported programming languages

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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

Java, Javascript

user defined functions and aggregates, HTTP Server extensions in Java

yes

Triggers

Hooks

yes

via event handlers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationship in graphs

yes

relationships in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles; record level security configurable

Access rights for users and roles

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

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, Matthias Gelbmann

show all

Recent citations in the news

Top 8 Best NoSQL Databases in 2024
9 September 2024, AIM

Comparing Graph Databases II. Part 2: ArangoDB, OrientDB, and… | by Sam Bell
20 September 2019, Towards Data Science

OrientDB: A Flexible and Scalable Multi-Model NoSQL DBMS
21 January 2022, Open Source For You

The 12 Best Graph Databases to Consider for 2024
22 October 2023, Solutions Review

K2View updates DataOps platform with data fabric automation
11 May 2021, TechTarget

provided by Google News

A Look at Valentina
18 April 2014, SitePoint

MySQL GUI Tools for Windows and Ubuntu/Linux: Top 8 free or open source
7 December 2018, H2S Media

provided by Google News

Share this page