DBMS > FatDB vs. HEAVY.AI vs. PostGIS vs. Spark SQL vs. Transbase

System Properties Comparison FatDB vs. HEAVY.AI vs. PostGIS vs. Spark SQL vs. Transbase

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

Spatial extension of PostgreSQL

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

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

postgis.net

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

Technical documentation

docs.heavy.ai

postgis.net/documentation

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

FatCloud

HEAVY.AI, Inc.

Apache Software Foundation

Transaction Software GmbH

Initial release

2012

2016

2005

2014

1987

Current release

5.10, January 2022

3.4.2, February 2024

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL v2.0

Open Source

Apache 2.0

commercial

free development license

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

Scala

C and C++

Server operating systems

Windows

Linux

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

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

JDBC
ODBC
Thrift
Vega

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

user defined functions

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

yes

based on PostgreSQL

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes

based on PostgreSQL

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes

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

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Big Data Analytics: A Game Changer for Infrastructure
13 July 2023, Spiceworks News and Insights

HEAVY.AI Launches HEAVY 7.0, Introducing Real-Time Machine Learning Capabilities
19 April 2023, Business Wire

Making the most of geospatial intelligence
14 April 2023, InfoWorld

HEAVY.AI Partners with Bain, Maxar, and Nvidia to Provide Digital Twins for Telecom Networks
16 February 2023, Datanami

The insideBIGDATA IMPACT 50 List for Q4 2023
11 October 2023, insideBIGDATA

provided by Google News

Use Amazon Athena with Spark SQL for your open-source transactional table formats | Amazon Web Services
24 January 2024, AWS Blog

What is Apache Spark? The big data platform that crushed Hadoop
3 April 2024, InfoWorld

Cracking the Apache Spark Interview: 80+ Top Questions and Answers for 2024
1 April 2024, Simplilearn

Performant IPv4 Range Spark Joins | by Jean-Claude Cote
24 January 2024, Towards Data Science

Run Apache Hive workloads using Spark SQL with Amazon EMR on EKS | Amazon Web Services
18 October 2023, AWS Blog

provided by Google News

Share this page