DBMS > Geode vs. HEAVY.AI vs. IBM Db2 warehouse vs. jBASE vs. Microsoft SQL Server

System Properties Comparison Geode vs. HEAVY.AI vs. IBM Db2 warehouse vs. jBASE vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Cloud-based data warehousing service

A robust multi-value DBMS comprising development tools and middleware

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

geode.apache.org

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

www.ibm.com/products/db2/warehouse

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.microsoft.com/en-us/sql-server

Technical documentation

geode.apache.org/docs

docs.heavy.ai

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

learn.microsoft.com/en-US/sql/sql-server

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

HEAVY.AI, Inc.

IBM

Rocket Software (formerly Zumasys)

Microsoft

Initial release

2002

2016

2014

1991

1989

Current release

1.1, February 2017

5.10, January 2022

5.7

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

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

Java

C++ and CUDA

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

hosted

AIX
Linux
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

.NET Client API
JDBC
ODBC
OLE DB

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

All languages supporting JDBC/ODBC/Thrift
Python

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net
Basic
Jabbascript
Java

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

PL/SQL, SQL PL

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

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

User concepts

Access control

Access rights per client and object definable

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.