DBMS > Graph Engine vs. Infobright vs. Microsoft Azure Synapse Analytics vs. Snowflake vs. Tibero

System Properties Comparison Graph Engine vs. Infobright vs. Microsoft Azure Synapse Analytics vs. Snowflake vs. Tibero

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Graph DBMS
Key-value store

Relational DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.graphengine.io

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/services/synapse-analytics

www.snowflake.com

us.tmaxsoft.com/products/tibero

Technical documentation

www.graphengine.io/docs/manual

docs.microsoft.com/azure/synapse-analytics

docs.snowflake.net/manuals/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Microsoft

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Snowflake Computing Inc.

TmaxSoft

Initial release

2010

2005

2016

2014

2003

Current release

6, April 2015

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

C++

C and Assembler

Server operating systems

.NET

Linux
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

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

C#
Java
PHP

JavaScript (Node.js)
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

Transact SQL

user defined functions

Persistent Stored Procedure (PSM)

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding, horizontal partitioning

yes

horizontal partitioning

by range, hash, list or composite

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

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

planned for next version

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

yes

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.