DBMS > Faircom DB vs. Microsoft Azure Cosmos DB vs. Teradata vs. Trafodion

System Properties Comparison Faircom DB vs. Microsoft Azure Cosmos DB vs. Teradata vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Globally distributed, horizontally scalable, multi-model database service

A hybrid cloud data analytics software platform (Teradata Vantage)

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

www.faircom.com/products/faircom-db

azure.microsoft.com/services/cosmos-db

www.teradata.com

trafodion.apache.org

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

learn.microsoft.com/azure/cosmos-db

docs.teradata.com

trafodion.apache.org/documentation.html

Developer

FairCom Corporation

Microsoft

Teradata

Apache Software Foundation, originally developed by HP

Initial release

1979

2014

1984

2014

Current release

V12, November 2020

Teradata Vantage 1.0 MU2, January 2019

2.3.0, February 2019

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Apache 2.0

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

ANSI C, C++

C++, Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

hosted
Linux

Linux

Data scheme

schema free, schema optional, schema required, partial schema,

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

JSON types

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

yes

All properties auto-indexed by default

yes

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

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like query language

yes

SQL 2016 + extensions

yes

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

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

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

JavaScript

yes

UDFs, stored procedures, table functions in parallel

Java Stored Procedures

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

Implicit feature of the cloud service

Sharding

Hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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 with additional protections for files

Access rights can be defined down to the item level

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.