DBMS > GridGain vs. gStore vs. MySQL vs. PostGIS vs. SAP SQL Anywhere

System Properties Comparison GridGain vs. gStore vs. MySQL vs. PostGIS vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

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

A native Graph DBMS to store and maintain very large RDF datasets.

Widely used open source RDBMS

Spatial extension of PostgreSQL

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Key-value store
Relational DBMS

Graph DBMS
RDF store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

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

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

www.gridgain.com/docs/index.html

en.gstore.cn/#/enDocs

dev.mysql.com/doc

postgis.net/documentation

help.sap.com/docs/SAP_SQL_Anywhere

Developer

GridGain Systems, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SAP

formerly Sybase

Initial release

2007

2016

1995

2005

1992

Current release

GridGain 8.5.1

1.2, November 2023

8.4.0, April 2024

3.4.2, February 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

commercial

Cloud-based only

Only available as a cloud service

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, C++, .Net

C++

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free and OWL/RDFS-schema support

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

yes

SQL

Support of SQL

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

yes

with proprietary extensions

yes

APIs and other access methods

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

HTTP API
SPARQL 1.1

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
PHP
Python

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++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

yes

proprietary syntax

user defined functions

yes, in C/C++, Java, .Net or Perl

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

ACID

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

Security Hooks for custom implementations

Users, roles and permissions, Role-Based Access Control (RBAC) supported

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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.