DBMS > GeoSpock vs. H2 vs. HyperSQL vs. IBM Cloudant vs. Snowflake

System Properties Comparison GeoSpock vs. H2 vs. HyperSQL vs. IBM Cloudant vs. Snowflake

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Database as a Service offering based on Apache CouchDB

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	3.23
Rank	#93	Overall
	#48	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

geospock.com

www.h2database.com

hsqldb.org

www.ibm.com/products/cloudant

www.snowflake.com

Technical documentation

www.h2database.com/html/main.html

hsqldb.org/web/hsqlDocsFrame.html

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

GeoSpock

Thomas Mueller

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Snowflake Computing Inc.

Initial release

2005

2001

2010

2014

Current release

2.0, September 2019

2.2.220, July 2023

2.7.2, June 2023

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

based on BSD license

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

Java, Javascript

Java

Erlang

Server operating systems

hosted

All OS with a Java VM

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

hosted

Data scheme

yes

schema-free

yes

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

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

JDBC
ODBC

HTTP API

JDBC via HTTP
JDBC
ODBC

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

Java

All languages supporting JDBC/ODBC
Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

Java, SQL

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

With clustering: 2 database servers on different computers operate on identical copies of a database

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Optimistic locking

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 for users can be defined per table

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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

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.