DBMS > Hypertable vs. Microsoft Azure Cosmos DB vs. PostGIS vs. Trafodion

System Properties Comparison Hypertable vs. Microsoft Azure Cosmos DB vs. PostGIS vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

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

Description

An open source BigTable implementation based on distributed file systems such as Hadoop

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

Transactional SQL-on-Hadoop DBMS

Primary database model

Wide column store

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

azure.microsoft.com/services/cosmos-db

postgis.net

trafodion.apache.org

Technical documentation

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

trafodion.apache.org/documentation.html

Developer

Hypertable Inc.

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2009

2014

2005

2014

Current release

0.9.8.11, March 2016

3.4.2, February 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

GNU version 3. Commercial license available

commercial

Open Source

GPL v2.0

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

C++

C++, Java

Server operating systems

Linux
OS X
Windows

an inofficial Windows port is available

hosted

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

restricted

only exact value or prefix value scans

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

C++ API
Thrift

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

ADO.NET
JDBC
ODBC

Supported programming languages

C++
Java
Perl
PHP
Python
Ruby

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

JavaScript

user defined functions

Java Stored Procedures

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor on file system level

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Immediate Consistency

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

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Access rights can be defined down to the item level

yes

based on PostgreSQL

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.