DBMS > ArcadeDB vs. GeoMesa

System Properties Comparison ArcadeDB vs. GeoMesa

Please select another system to include it in the comparison.

Our visitors often compare ArcadeDB and GeoMesa with Neo4j and PostgreSQL.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Spatial DBMS

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

Score	0.01
Rank	#379	Overall
	#53	Document stores
	#38	Graph DBMS
	#57	Key-value stores
	#39	Time Series DBMS

Score	0.80
Rank	#211	Overall
	#4	Spatial DBMS

Website

arcadedb.com

www.geomesa.org

Technical documentation

docs.arcadedb.com

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

Developer

Arcade Data

CCRi and others

Initial release

2021

2014

Current release

September 2021

5.0.1, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 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

Java

Scala

Server operating systems

All OS with a Java VM

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

Supported programming languages

Java

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Foreign keys

Referential integrity

yes

relationship in graphs

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

User concepts

Access control

yes

depending on the DBMS used for storage

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.