DBMS > GeoSpock vs. GigaSpaces vs. IRONdb vs. Snowflake

System Properties Comparison GeoSpock vs. GigaSpaces vs. IRONdb 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.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial and temporal data processing engine for extreme data scale

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Graph DBMS
Search engine

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

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

geospock.com

www.gigaspaces.com

www.circonus.com/solutions/time-series-database/

www.snowflake.com

Technical documentation

docs.gigaspaces.com/latest/landing.html

docs.circonus.com/irondb/category/getting-started

docs.snowflake.net/manuals/index.html

Developer

GeoSpock

Gigaspaces Technologies

Circonus LLC.

Snowflake Computing Inc.

Initial release

2000

2017

2014

Current release

2.0, September 2019

15.5, September 2020

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses 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, Javascript

Java, C++, .Net

C and C++

Server operating systems

hosted

Linux
macOS
Solaris
Windows

Linux

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

XML can be used for describing objects metadata

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-99 for query and DML statements

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

JDBC

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C++
Java
Python
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

yes, in Lua

user defined functions

Triggers

yes, event driven architecture

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Automatic, metric affinity per node

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate consistency per node, eventual consistency across nodes

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

User concepts

Access control

Access rights for users can be defined per table

Role-based access control

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.