DBMS > Amazon Redshift vs. OrigoDB vs. TigerGraph vs. Yanza

System Properties Comparison Amazon Redshift vs. OrigoDB vs. TigerGraph 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

A fully ACID in-memory object graph database

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Graph DBMS

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	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

origodb.com

www.tigergraph.com

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

origodb.com/docs

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Robert Friberg et al

Yanza

Initial release

2012

2009

under the name LiveDB

2017

2015

License

Commercial or Open Source

commercial

Open Source

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

C++

Server operating systems

hosted

Linux
Windows

Linux

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Domain Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

depending on model

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

Write ahead log

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

Role based authorization

Role-based access control

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.