DBMS > AllegroGraph vs. Amazon Redshift vs. Apache Phoenix vs. Sadas Engine vs. Yanza

System Properties Comparison AllegroGraph vs. Amazon Redshift vs. Apache Phoenix vs. Sadas Engine vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded 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 scale-out RDBMS with evolutionary schema built on Apache HBase

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Time Series DBMS for IoT Applications

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

allegrograph.com

aws.amazon.com/redshift

phoenix.apache.org

www.sadasengine.com

yanza.com

Technical documentation

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

docs.aws.amazon.com/redshift

phoenix.apache.org

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Franz Inc.

Amazon (based on PostgreSQL)

Apache Software Foundation

SADAS s.r.l.

Yanza

Initial release

2004

2012

2014

2006

2015

Current release

8.0, December 2023

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

8.0

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

Apache Version 2.0

commercial

free trial version available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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

Linux
Unix
Windows

AIX
Linux
Windows

Windows

Data scheme

yes

RDF schemas

yes

late-bound, schema-on-read capabilities

yes

schema-free

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

restricted

yes

SQL

Support of SQL

SPARQL is used as query language

yes

does not fully support an SQL-standard

yes

APIs and other access methods

RESTful HTTP API
SPARQL

JDBC
ODBC

JDBC

JDBC
ODBC
Proprietary protocol

HTTP API

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

All languages supporting JDBC/ODBC

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
C
C#
C++
Groovy
Java
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

JavaScript or Common Lisp

user defined functions

in Python

user defined functions

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

with Federation

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

In-memory capabilities

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

yes

managed by 'Learn by Usage'

User concepts

Access control

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

fine grained access rights according to SQL-standard

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access rights for users, groups and roles 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

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.