DBMS > AllegroGraph vs. Google BigQuery vs. Memcached vs. VoltDB

System Properties Comparison AllegroGraph vs. Google BigQuery vs. Memcached vs. VoltDB

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

Large scale data warehouse service with append-only tables

In-memory key-value store, originally intended for caching

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

allegrograph.com

cloud.google.com/bigquery

www.memcached.org

www.voltdb.com

Technical documentation

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

cloud.google.com/bigquery/docs

github.com/memcached/memcached/wiki

docs.voltdb.com

Developer

Franz Inc.

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

VoltDB Inc.

Initial release

2004

2010

2003

2010

Current release

8.0, December 2023

1.6.27, May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

BSD license

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Unix
Windows

Linux
OS X

for development

Data scheme

yes

RDF schemas

yes

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.

bulk load of XML files possible

Secondary indexes

yes

SQL

Support of SQL

SPARQL is used as query language

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP API
SPARQL

RESTful HTTP/JSON API

Proprietary protocol

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

user defined functions

in JavaScript

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

with Federation

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

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

Google Cloud Identity & Access Management (IAM)

yes

using SASL (Simple Authentication and Security Layer) protocol

Users and roles with access to stored procedures

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

How a Neuro-Symbolic AI Approach Can Improve Trust in AI Apps
23 May 2024

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

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.