DBMS > Apache Phoenix vs. Elasticsearch vs. GeoSpock vs. Snowflake

System Properties Comparison Apache Phoenix vs. Elasticsearch vs. GeoSpock vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Spatial and temporal data processing engine for extreme data scale

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

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Time Series DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

phoenix.apache.org

www.elastic.co/elasticsearch

geospock.com

www.snowflake.com

Technical documentation

phoenix.apache.org

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Elastic

GeoSpock

Snowflake Computing Inc.

Initial release

2014

2010

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

8.6, January 2023

2.0, September 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Elastic 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

Java, Javascript

Server operating systems

Linux
Unix
Windows

All OS with a Java VM

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

temporal, categorical

SQL

Support of SQL

yes

SQL-like query language

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

Java API
RESTful HTTP/JSON API

JDBC

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

In-memory capabilities

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

yes

Memcached and Redis integration

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access rights for users can be defined per table

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.