DBMS > GeoSpock vs. Heroic vs. IBM Cloudant vs. OrientDB vs. SQLite

System Properties Comparison GeoSpock vs. Heroic vs. IBM Cloudant vs. OrientDB vs. SQLite

Editorial information provided by DB-Engines

Name

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

Description

Spatial and temporal data processing engine for extreme data scale

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

Database as a Service offering based on Apache CouchDB

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Document store

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

geospock.com

github.com/spotify/heroic

www.ibm.com/products/cloudant

orientdb.org

www.sqlite.org

Technical documentation

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

Developer

GeoSpock

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

2014

2010

2000

Current release

2.0, September 2019

3.2.29, March 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache version 2

Open Source

Public Domain

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

Erlang

Java

Server operating systems

hosted

All OS with a Java JDK (>= JDK 6)

server-less

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

temporal, categorical

yes

via Elasticsearch

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

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

RESTful HTTP/JSON API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Java, Javascript

Triggers

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

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

Access rights for users can be defined per database

Access rights for users and roles; record level security configurable

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.