DBMS > AllegroGraph vs. Dolt vs. GeoMesa vs. Google BigQuery

System Properties Comparison AllegroGraph vs. Dolt vs. GeoMesa vs. Google BigQuery

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

A MySQL compatible DBMS with Git-like versioning of data and schema

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

Large scale data warehouse service with append-only tables

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store

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.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

allegrograph.com

github.com/dolthub/dolt
www.dolthub.com

www.geomesa.org

cloud.google.com/bigquery

Technical documentation

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

docs.dolthub.com

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

cloud.google.com/bigquery/docs

Developer

Franz Inc.

DoltHub Inc

CCRi and others

Google

Initial release

2004

2018

2014

2010

Current release

8.0, December 2023

4.0.5, February 2024

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

commercial

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

Server operating systems

Linux
OS X
Windows

Linux
macOS
Windows

hosted

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

Secondary indexes

yes

SQL

Support of SQL

SPARQL is used as query language

yes

APIs and other access methods

RESTful HTTP API
SPARQL

CLI Client
HTTP REST

RESTful HTTP/JSON 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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

yes

currently in alpha release

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

with Federation

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

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 or Eventual Consistency depending on configuration

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

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

Only one user is configurable, and must be specified in the config file at startup

yes

depending on the DBMS used for storage

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

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.