DBMS > Infobright vs. MySQL vs. Teradata vs. TerminusDB

System Properties Comparison Infobright vs. MySQL vs. Teradata vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.mysql.com

www.teradata.com

terminusdb.com

Technical documentation

dev.mysql.com/doc

docs.teradata.com

terminusdb.github.io/terminusdb/#

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Teradata

DataChemist Ltd.

Initial release

2005

1995

1984

2018

Current release

9.0.0, July 2024

Teradata Vantage 1.0 MU2, January 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

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

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Prolog, Rust

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted
Linux

Linux

Data scheme

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

with proprietary extensions

yes

SQL 2016 + extensions

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Hashing

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Journaling Streams

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

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

no user groups or roles

fine grained access rights according to SQL-standard

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.