DBMS > GeoSpock vs. Google Cloud Bigtable vs. GridGain vs. SAP HANA vs. Tibero

System Properties Comparison GeoSpock vs. Google Cloud Bigtable vs. GridGain vs. SAP HANA vs. Tibero

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

GridGain is an in-memory computing platform, built on Apache Ignite

In-memory, column based data store. Available as appliance or cloud service

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

Key-value store
Wide column store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

geospock.com

cloud.google.com/bigtable

www.gridgain.com

www.sap.com/products/hana.html

us.tmaxsoft.com/products/tibero

Technical documentation

cloud.google.com/bigtable/docs

www.gridgain.com/docs/index.html

help.sap.com/hana

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

GeoSpock

Google

GridGain Systems, Inc.

SAP

TmaxSoft

Initial release

2015

2007

2010

2003

Current release

2.0, September 2019

GridGain 8.5.1

2.0 SPS07 (April 4, 2023), April 2023

6, April 2015

License

Commercial or Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Javascript

Java, C++, .Net

C and Assembler

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Appliance or cloud-service

AIX
HP-UX
Linux
Solaris
Windows

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

JDBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

SQLScript, R

Persistent Stored Procedure (PSM)

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes (replicated cache)

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

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

planned for next version

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)

Security Hooks for custom implementations

yes

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.