DBMS > GeoMesa vs. JanusGraph vs. Microsoft Azure AI Search vs. Oracle

System Properties Comparison GeoMesa vs. JanusGraph vs. Microsoft Azure AI Search vs. Oracle

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

Search-as-a-service for web and mobile app development

Widely used RDBMS

Primary database model

Secondary database models

Vector DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

www.geomesa.org

janusgraph.org

azure.microsoft.com/en-us/services/search

www.oracle.com/database

Technical documentation

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

docs.janusgraph.org

learn.microsoft.com/en-us/azure/search

docs.oracle.com/en/database

Developer

CCRi and others

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Oracle

Initial release

2014

2017

2015

1980

Current release

5.0.0, May 2024

0.6.3, February 2023

23c, September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Java

C and C++

Server operating systems

Linux
OS X
Unix
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Clojure
Java
Python

C#
Java
JavaScript
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

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)

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

can be realized in PL/SQL

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

Transaction concepts

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

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

yes

depending on the DBMS used for storage

User authentification and security via Rexster Graph Server

yes

using Azure authentication

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.