DBMS > AllegroGraph vs. Microsoft Azure Table Storage vs. SQLite vs. Vitess

System Properties Comparison AllegroGraph vs. Microsoft Azure Table Storage vs. SQLite vs. Vitess

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 Wide Column Store for rapid development using massive semi-structured datasets

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
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	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

allegrograph.com

azure.microsoft.com/en-us/services/storage/tables

www.sqlite.org

vitess.io

Technical documentation

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

www.sqlite.org/docs.html

vitess.io/docs

Developer

Franz Inc.

Microsoft

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2004

2012

2000

2013

Current release

8.0, December 2023

3.45.3 (15 April 2024), April 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux
OS X
Windows

hosted

server-less

Docker
Linux
macOS

Data scheme

yes

RDF schemas

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API
SPARQL

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

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

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

optimistic locking

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

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

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or roles

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.