DBMS > GeoSpock vs. H2 vs. ITTIA vs. SQLite vs. Trafodion

System Properties Comparison GeoSpock vs. H2 vs. ITTIA vs. SQLite vs. Trafodion

Editorial information provided by DB-Engines

Name

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

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Edge Time Series DBMS with Real-Time Stream Processing

Widely used embeddable, in-process RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

Relational DBMS

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

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.44
Rank	#267	Overall
	#23	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

geospock.com

Technical documentation

www.h2database.com/html/main.html

www.sqlite.org/docs.html

trafodion.apache.org/documentation.html

Developer

GeoSpock

Thomas Mueller

ITTIA L.L.C.

Dwayne Richard Hipp

Apache Software Foundation, originally developed by HP

Initial release

2005

2007

2000

2014

Current release

2.0, September 2019

2.2.220, July 2023

8.7

3.46.0 (23 May 2024), May 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Open Source

Public Domain

Open Source

Apache 2.0

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 and C++

C++, Java

Server operating systems

hosted

All OS with a Java VM

Linux
Windows

server-less

Linux

Data scheme

yes

Fixed schema

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API
WebSocket

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC

Supported programming languages

Java

C
C++
JavaScript (Node.js)
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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

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

fine grained access rights according to SQL-standard

Database file passwords

fine grained access rights according to SQL-standard

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.