DBMS > Apache Drill vs. GeoSpock vs. Hive vs. Ignite vs. Snowflake

System Properties Comparison Apache Drill vs. GeoSpock vs. Hive vs. Ignite 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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Spatial and temporal data processing engine for extreme data scale

data warehouse software for querying and managing large distributed datasets, built on Hadoop

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.

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

geospock.com

Technical documentation

drill.apache.org/docs

cwiki.apache.org/confluence/display/Hive/Home

apacheignite.readme.io/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

GeoSpock

Apache Software Foundation

initially developed by Facebook

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2012

2015

2014

Current release

1.20.3, January 2023

2.0, September 2019

3.1.3, April 2022

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2

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

Java

C++, Java, .Net

Server operating systems

Linux
OS X
Windows

hosted

All OS with a Java VM

Linux
OS X
Solaris
Windows

hosted

Data scheme

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

SQL SELECT statement is SQL:2003 compliant

ANSI SQL for query only (using Presto)

SQL-like DML and DDL statements

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

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

JDBC
ODBC
Thrift

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

CLI Client
JDBC
ODBC

Supported programming languages

C++

C++
Java
PHP
Python

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions and integration of map-reduce

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

user defined functions

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Access rights for users can be defined per table

Access rights for users, groups and roles

Security Hooks for custom implementations

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.