DBMS > CouchDB vs. GeoSpock vs. Graphite vs. Heroic vs. Snowflake

System Properties Comparison CouchDB vs. GeoSpock vs. Graphite vs. Heroic 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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Spatial and temporal data processing engine for extreme data scale

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Time Series DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

couchdb.apache.org

geospock.com

github.com/graphite-project/graphite-web

github.com/spotify/heroic

www.snowflake.com

Technical documentation

docs.couchdb.org/en/stable

graphite.readthedocs.io

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

GeoSpock

Chris Davis

Spotify

Snowflake Computing Inc.

Initial release

2005

2006

2014

Current release

3.3.3, December 2023

2.0, September 2019

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache 2.0

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

Erlang

Java, Javascript

Python

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux
Unix

hosted

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

Numeric data only

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

via views

temporal, categorical

yes

via Elasticsearch

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC

HTTP API
Sockets

HQL (Heroic Query Language, a JSON-based language)
HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Automatic sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

locking

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.

User concepts

Access control

Access rights for users can be defined per database

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.