DBMS > GeoSpock vs. Google Cloud Datastore vs. Hyprcubd vs. MySQL vs. Oracle

System Properties Comparison GeoSpock vs. Google Cloud Datastore vs. Hyprcubd vs. MySQL vs. Oracle

Editorial information provided by DB-Engines

Name

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

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Serverless Time Series DBMS

Widely used open source RDBMS

Widely used RDBMS

Primary database model

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

geospock.com

cloud.google.com/datastore

hyprcubd.com (offline)

www.mysql.com

www.oracle.com/database

Technical documentation

cloud.google.com/datastore/docs

dev.mysql.com/doc

docs.oracle.com/en/database

Developer

GeoSpock

Google

Hyprcubd, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Initial release

2008

1995

1980

Current release

2.0, September 2019

8.4.0, April 2024

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is available

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

C and C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes

yes, details here

yes

time, int, uint, float, string

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language (GQL)

SQL-like query language

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JDBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

gRPC (https)

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

using Google App Engine

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Access rights for users can be defined per table

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

token access

Users with fine-grained authorization concept

no user groups or roles

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.