DBMS > GeoSpock vs. GigaSpaces vs. MySQL vs. SpaceTime

System Properties Comparison GeoSpock vs. GigaSpaces vs. MySQL vs. SpaceTime

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Widely used open source RDBMS

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Time Series DBMS

Graph DBMS
Search engine

Document store
Spatial DBMS

Relational DBMS

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

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

geospock.com

www.gigaspaces.com

www.mysql.com

www.mireo.com/spacetime

Technical documentation

docs.gigaspaces.com/latest/landing.html

dev.mysql.com/doc

Developer

GeoSpock

Gigaspaces Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Mireo

Initial release

2000

1995

2020

Current release

2.0, September 2019

15.5, September 2020

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java, Javascript

Java, C++, .Net

C and C++

C++

Server operating systems

hosted

Linux
macOS
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

XML can be used for describing objects metadata

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-99 for query and DML statements

yes

with proprietary extensions

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

.Net
C++
Java
Python
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
C++
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Multi-source replication
Source-replica replication

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

yes

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.