DBMS > H2GIS vs. Memcached vs. RavenDB vs. Snowflake vs. SQream DB

System Properties Comparison H2GIS vs. Memcached vs. RavenDB vs. Snowflake vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

In-memory key-value store, originally intended for caching

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Secondary database models

Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

Technical documentation

www.h2gis.org/docs/home

github.com/memcached/memcached/wiki

ravendb.net/docs

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

CNRS

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Hibernating Rhinos

Snowflake Computing Inc.

SQream Technologies

Initial release

2013

2003

2010

2014

2017

Current release

1.6.27, May 2024

5.4, July 2022

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

LGPL 3.0

Open Source

BSD license

Open Source

AGPL version 3, commercial license available

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

SQL-like query language (RQL)

yes

APIs and other access methods

Proprietary protocol

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

Java

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

based on H2

yes

user defined functions

user defined functions in Python

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

yes

based on H2

yes

using SASL (Simple Authentication and Security Layer) protocol

Authorization levels configured per client 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.