DBMS > FatDB vs. HEAVY.AI vs. HyperSQL vs. Oracle

System Properties Comparison FatDB vs. HEAVY.AI vs. HyperSQL vs. Oracle

Please select another system to include it in the comparison.

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

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

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Widely used RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

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

hsqldb.org

www.oracle.com/database

Technical documentation

docs.heavy.ai

hsqldb.org/web/hsqlDocsFrame.html

docs.oracle.com/en/database

Developer

FatCloud

HEAVY.AI, Inc.

Oracle

Initial release

2012

2016

2001

1980

Current release

5.10, January 2022

2.7.2, June 2023

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

based on BSD license

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++ and CUDA

Java

C and C++

Server operating systems

Windows

Linux

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

with proprietary extensions

APIs and other access methods

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

JDBC
ODBC
Thrift
Vega

HTTP API

JDBC via HTTP
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

All languages supporting JDBC/ODBC
Java

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

via applications

Java, SQL

PL/SQL

also stored procedures in Java possible

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Can implement custom security layer via applications

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.