DBMS > Blueflood vs. Elasticsearch vs. EXASOL vs. GeoSpock vs. Snowflake

System Properties Comparison Blueflood vs. Elasticsearch vs. EXASOL vs. GeoSpock 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

Scalable TimeSeries DBMS based on Cassandra

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Spatial and temporal data processing engine for extreme data scale

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

Primary database model

Time Series 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	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

blueflood.io

www.elastic.co/elasticsearch

www.exasol.com

geospock.com

www.snowflake.com

Technical documentation

github.com/rax-maas/blueflood/wiki

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

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

Developer

Rackspace

Elastic

Exasol

GeoSpock

Snowflake Computing Inc.

Initial release

2013

2010

2000

2014

Current release

8.6, January 2023

2.0, September 2019

License

Commercial or Open Source

Open Source

Apache 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
OS X

All OS with a Java VM

hosted

Data scheme

predefined scheme

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

yes

temporal, categorical

SQL

Support of SQL

SQL-like query language

yes

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

HTTP REST

Java API
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

JDBC

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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.

Memcached and Redis integration

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

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.