DBMS > AllegroGraph vs. Amazon Redshift vs. IRONdb vs. Teradata Aster vs. TinkerGraph

System Properties Comparison AllegroGraph vs. Amazon Redshift vs. IRONdb vs. Teradata Aster vs. TinkerGraph

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Large scale data warehouse service for use with business intelligence tools

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Platform for big data analytics on multistructured data sources and types

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Secondary database models

Spatial DBMS

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

Score	1.16
Rank	#179	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

allegrograph.com

aws.amazon.com/redshift

www.circonus.com/solutions/time-series-database/

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

docs.aws.amazon.com/redshift

docs.circonus.com/irondb/category/getting-started

Developer

Franz Inc.

Amazon (based on PostgreSQL)

Circonus LLC.

Teradata

Initial release

2004

2012

2017

2005

2009

Current release

8.0, December 2023

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

Apache 2.0

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

C and C++

Java

Server operating systems

Linux
OS X
Windows

hosted

Linux

Data scheme

yes

RDF schemas

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

in Aster File Store

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SPARQL is used as query language

yes

does not fully support an SQL-standard

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

RESTful HTTP API
SPARQL

JDBC
ODBC

HTTP API

ADO.NET
JDBC
ODBC
OLE DB

TinkerPop 3

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

All languages supporting JDBC/ODBC

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C#
C++
Java
Python
R

Groovy
Java

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

user defined functions

in Python

yes, in Lua

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

with Federation

Sharding

Automatic, metric affinity per node

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

configurable replication factor, datacenter aware

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency or Eventual Consistency depending on configuration

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships 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

optional

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

fine grained access rights according to SQL-standard

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.