DBMS > Apache Phoenix vs. FatDB vs. Oracle Rdb vs. Snowflake vs. Teradata Aster

System Properties Comparison Apache Phoenix vs. FatDB vs. Oracle Rdb vs. Snowflake vs. Teradata Aster

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

phoenix.apache.org

www.oracle.com/database/technologies/related/rdb.html

www.snowflake.com

Technical documentation

phoenix.apache.org

www.oracle.com/database/technologies/related/rdb-doc.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

FatCloud

Oracle, originally developed by Digital Equipment Corporation (DEC)

Snowflake Computing Inc.

Teradata

Initial release

2014

2012

1984

2014

2005

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Java

Server operating systems

Linux
Unix
Windows

Windows

HP Open VMS

hosted

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

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

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

yes

via applications

user defined functions

R packages

Triggers

yes

via applications

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Can implement custom security layer via applications

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.