DBMS > HEAVY.AI vs. Oracle NoSQL vs. Snowflake vs. TempoIQ

System Properties Comparison HEAVY.AI vs. Oracle NoSQL vs. Snowflake vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

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

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.oracle.com/database/nosql/technologies/nosql

www.snowflake.com

tempoiq.com (offline)

Technical documentation

docs.heavy.ai

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

Oracle

Snowflake Computing Inc.

TempoIQ

Initial release

2016

2011

2014

2012

Current release

5.10, January 2022

23.3, December 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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++ and CUDA

Java

Server operating systems

Linux

Linux
Solaris SPARC/x86

hosted

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

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

schema-free

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.