DBMS > H2GIS vs. HEAVY.AI vs. Ignite vs. Microsoft Azure AI Search vs. Snowflake

System Properties Comparison H2GIS vs. HEAVY.AI vs. Ignite vs. Microsoft Azure AI Search vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Search-as-a-service for web and mobile app development

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

Primary database model

Spatial DBMS

Relational DBMS

Key-value store
Relational DBMS

Search engine

Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS

Vector DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.h2gis.org

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

ignite.apache.org

azure.microsoft.com/en-us/services/search

www.snowflake.com

Technical documentation

www.h2gis.org/docs/home

docs.heavy.ai

apacheignite.readme.io/docs

learn.microsoft.com/en-us/azure/search

docs.snowflake.net/manuals/index.html

Developer

CNRS

HEAVY.AI, Inc.

Apache Software Foundation

Microsoft

Snowflake Computing Inc.

Initial release

2013

2016

2015

2014

Current release

5.10, January 2022

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

LGPL 3.0

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

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++ and CUDA

C++, Java, .Net

Server operating systems

Linux

Linux
OS X
Solaris
Windows

hosted

Data scheme

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

yes

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Java

All languages supporting JDBC/ODBC/Thrift
Python

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

based on H2

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

Multi-source replication

yes (replicated cache)

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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, 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

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

yes

using Azure authentication

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.