DBMS > Altibase vs. Amazon Redshift vs. FatDB vs. RavenDB vs. TimesTen

System Properties Comparison Altibase vs. Amazon Redshift vs. FatDB vs. RavenDB vs. TimesTen

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.

Description

An enterprise grade, high-performance RDBMS

Large scale data warehouse service for use with business intelligence tools

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

In-Memory RDBMS compatible to Oracle

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.07
Rank	#186	Overall
	#87	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

altibase.com

aws.amazon.com/redshift

ravendb.net

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

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

docs.aws.amazon.com/redshift

ravendb.net/docs

docs.oracle.com/database/timesten-18.1

Developer

Altibase

Amazon (based on PostgreSQL)

FatCloud

Hibernating Rhinos

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

1999

2012

2010

1998

Current release

v7.3, 2023, August 2023

5.4, July 2022

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

AGPL version 3, commercial license available

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

C++

Server operating systems

AIX
HP-UX
Linux

hosted

Windows

Linux
macOS
Raspberry Pi
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

ANSI SQL-92

yes

does not fully support an SQL-standard

Via inetgration in SQL Server

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
ODBC

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C
C++
Java

All languages supporting JDBC/ODBC

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

stored procedures and stored functions

user defined functions

in Python

yes

via applications

yes

PL/SQL

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

Can implement custom security layer via applications

Authorization levels configured per client per database

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.