DBMS > Graph Engine vs. Infobright vs. Snowflake vs. Teradata

System Properties Comparison Graph Engine vs. Infobright vs. Snowflake vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Cloud-based data warehousing service for structured and semi-structured data

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

www.graphengine.io

ignitetech.com/softwarelibrary/infobrightdb

www.snowflake.com

www.teradata.com

Technical documentation

www.graphengine.io/docs/manual

docs.snowflake.net/manuals/index.html

docs.teradata.com

Developer

Microsoft

Ignite Technologies Inc.; formerly InfoBright Inc.

Snowflake Computing Inc.

Teradata

Initial release

2010

2005

2014

1984

Current release

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

MIT License

commercial

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

commercial

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

.NET and C

Server operating systems

.NET

Linux
Windows

hosted

hosted
Linux

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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.

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C#
C++
F#
Visual Basic

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

JavaScript (Node.js)
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

yes

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

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

Foreign keys

Referential integrity

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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

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.