DBMS > Amazon Redshift vs. Infobright vs. Stardog vs. Yanza

System Properties Comparison Amazon Redshift vs. Infobright vs. Stardog vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Large scale data warehouse service for use with business intelligence tools

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Graph DBMS
RDF store

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

aws.amazon.com/redshift

ignitetech.com/softwarelibrary/infobrightdb

www.stardog.com

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

docs.stardog.com

Developer

Amazon (based on PostgreSQL)

Ignite Technologies Inc.; formerly InfoBright Inc.

Stardog-Union

Yanza

Initial release

2012

2005

2010

2015

Current release

7.3.0, May 2020

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Server operating systems

hosted

Linux
Windows

Linux
macOS
Windows

Windows

Data scheme

yes

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

restricted

Knowledge Grid Technology used instead

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication in HA-Cluster

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Immediate Consistency

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

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users and roles

More information provided by the system vendor

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.