DBMS > AllegroGraph vs. GeoMesa vs. MySQL vs. ObjectBox

System Properties Comparison AllegroGraph vs. GeoMesa vs. MySQL vs. ObjectBox

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance, persistent RDF store with additional support for Graph DBMS

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

Widely used open source RDBMS

Extremely fast embedded database for small devices, IoT and Mobile

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Object oriented DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

Time Series DBMS

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

Score	1.06
Rank	#187	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Website

Technical documentation

franz.com/agraph/support/documentation/current/agraph-introduction.html

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

dev.mysql.com/doc

docs.objectbox.io

Developer

Franz Inc.

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

ObjectBox Limited

Initial release

2004

2014

1995

2017

Current release

8.0, December 2023

4.0.5, February 2024

8.3.0, January 2024

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

C and C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Android
iOS
Linux
macOS
Windows

Data scheme

yes

RDF schemas

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.

bulk load of XML files possible

yes

Secondary indexes

yes

SQL

Support of SQL

SPARQL is used as query language

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API
SPARQL

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary native API

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

with Federation

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

Multi-source replication
Source-replica replication

online/offline synchronization between client and server

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or roles

yes

More information provided by the system vendor

Specific characteristics

Knowledge Graph Platform Leader FedShard - Designed for Entity-Event Knowledge Graph...
» more

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» more

News

Can Neuro-Symbolic AI Solve AI’s Weaknesses?
17 April 2024

100 Companies That Matter in KM – Franz Inc.
3 April 2024

Exploring AllegroGraph v8 – Unleashing the Power of Neuro-Symbolic AI (Recorded Webinar)
9 February 2024

What is Neuro-Symbolic AI?
23 January 2024

Allegro CL v11 – Now Available! – The Neuro-Symbolic AI Programming Platform
8 January 2024

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

Vector Database Release for Flutter / Dart + Python
13 June 2023

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.