DBMS > BigchainDB vs. GeoMesa vs. HEAVY.AI vs. HyperSQL vs. Microsoft SQL Server

System Properties Comparison BigchainDB vs. GeoMesa vs. HEAVY.AI vs. HyperSQL vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Microsofts flagship relational DBMS

Primary database model

Document store

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	3.90
Rank	#85	Overall
	#46	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

www.bigchaindb.com

www.geomesa.org

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

hsqldb.org

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.geomesa.org/documentation/stable/user/index.html

docs.heavy.ai

hsqldb.org/web/hsqlDocsFrame.html

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

Developer

CCRi and others

HEAVY.AI, Inc.

Microsoft

Initial release

2016

2014

2016

2001

1989

Current release

4.0.5, February 2024

5.10, January 2022

2.7.2, June 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache License 2.0

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

Python

Scala

C++ and CUDA

Java

C++

Server operating systems

Linux

All OS with a Java VM

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

Linux
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

yes

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

HTTP API

JDBC via HTTP
JDBC
ODBC

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

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

All languages supporting JDBC/ODBC
Java

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

Server-side scripts

Stored procedures

Java, SQL

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Round robin

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

Multi-source replication

none

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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.