DBMS > AnzoGraph DB vs. GeoMesa vs. Microsoft Azure Synapse Analytics vs. RocksDB vs. Warp 10

System Properties Comparison AnzoGraph DB vs. GeoMesa vs. Microsoft Azure Synapse Analytics vs. RocksDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

cambridgesemantics.com/anzograph

www.geomesa.org

azure.microsoft.com/services/synapse-analytics

rocksdb.org

www.warp10.io

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

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

docs.microsoft.com/azure/synapse-analytics

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Cambridge Semantics

CCRi and others

Microsoft

Facebook, Inc.

SenX

Initial release

2018

2014

2016

2013

2015

Current release

2.3, January 2021

5.0.0, May 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache License 2.0

commercial

Open Source

BSD

Open Source

Apache License 2.0

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

C++

Java

Server operating systems

Linux

hosted

Linux

Linux
OS X
Windows

Data scheme

Schema-free and OWL/RDFS-schema support

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

ADO.NET
JDBC
ODBC

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

C++
Java
Python

C#
Java
PHP

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

Transact SQL

yes

WarpScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

depending on storage layer

Sharding, horizontal partitioning

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

depending on storage layer

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

depending on storage layer

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

not needed in graphs

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

ACID

yes

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.

yes

depending on storage layer

yes

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.