DBMS > GeoSpock vs. IBM Db2 vs. Sequoiadb vs. SQLite

System Properties Comparison GeoSpock vs. IBM Db2 vs. Sequoiadb 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

Common in IBM host environments, 2 different versions for host and Windows/Linux

NewSQL database with distributed OLTP and SQL

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Document store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

geospock.com

www.ibm.com/products/db2

www.sequoiadb.com

www.sqlite.org

Technical documentation

www.ibm.com/docs/en/db2

www.sequoiadb.com/en/index.php?m=Files&a=index

www.sqlite.org/docs.html

Developer

GeoSpock

IBM

Sequoiadb Ltd.

Dwayne Richard Hipp

Initial release

1983

host version

2013

2000

Current release

2.0, September 2019

12.1, October 2016

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free version is available

Open Source

Server: AGPL; Client: Apache V2

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

C and C++

C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
C++
Java
PHP
Python

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

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

only with Windows/Unix/Linux Version

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

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

simple password-based access control

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.