DBMS > Amazon Redshift vs. CouchDB vs. HEAVY.AI vs. Ingres vs. TempoIQ

System Properties Comparison Amazon Redshift vs. CouchDB vs. HEAVY.AI vs. Ingres vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Well established RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Website

aws.amazon.com/redshift

couchdb.apache.org

github.com/heavyai/heavydb
www.heavy.ai

www.actian.com/databases/ingres

tempoiq.com (offline)

Technical documentation

docs.aws.amazon.com/redshift

docs.couchdb.org/en/stable

docs.heavy.ai

docs.actian.com/ingres

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

HEAVY.AI, Inc.

Actian Corporation

TempoIQ

Initial release

2012

2005

2016

1974

originally developed at University Berkely in early 1970s

2012

Current release

3.3.3, December 2023

5.10, January 2022

11.2, May 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache Version 2; enterprise edition 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

Erlang

C++ and CUDA

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

All languages supporting JDBC/ODBC/Thrift
Python

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

yes

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Round robin

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

Ingres Replicator

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

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

MVCC

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

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

simple authentication-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.