DBMS > GeoSpock vs. Ingres vs. Riak KV vs. SQLite

System Properties Comparison GeoSpock vs. Ingres vs. Riak KV vs. SQLite

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

Spatial and temporal data processing engine for extreme data scale

Well established RDBMS

Distributed, fault tolerant key-value store

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

geospock.com

www.actian.com/databases/ingres

www.sqlite.org

Technical documentation

docs.actian.com/ingres

www.tiot.jp/riak-docs/riak/kv/latest

www.sqlite.org/docs.html

Developer

GeoSpock

Actian Corporation

OpenSource, formerly Basho Technologies

Dwayne Richard Hipp

Initial release

1974

originally developed at University Berkely in early 1970s

2009

2000

Current release

2.0, September 2019

11.2, May 2022

3.2.0, December 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
OS X

server-less

Data scheme

yes

schema-free

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

temporal, categorical

yes

restricted

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

fine grained access rights according to SQL-standard

yes, using Riak Security

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.