DBMS > Alibaba Cloud PolarDB vs. GeoSpock vs. MySQL vs. TerminusDB

System Properties Comparison Alibaba Cloud PolarDB vs. GeoSpock vs. MySQL vs. TerminusDB

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

A cloud-native relational database compatible with MySQL, PostgreSQL, and Oracle. Designed for business critical applications.

Spatial and temporal data processing engine for extreme data scale

Widely used open source RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Document store
RDF store

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

Score	0.66
Rank	#235	Overall
	#108	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.alibabacloud.com/product/polardb

geospock.com

www.mysql.com

terminusdb.com

Technical documentation

www.alibabacloud.com/help/en/polardb/product-overview

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

Alibaba

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

1995

2018

Current release

2.0, September 2019

8.4.0, April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

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

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Java
Python

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Automatic sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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 journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

More information provided by the system vendor

Specific characteristics

PolarDB, previously ApsaraDB for PolarDB, is a cloud-native relational database designed...
» more

Competitive advantages

Webinar: Top Scientists Live: Tech Secrets to Double 11's Success Revealed. White...
» more

Typical application scenarios

Creating a Robust Cloud-Based Database for Fintech, E-Commerce and Gaming. Learn...
» more

Licensing and pricing models

Specification and pricing. You can use either of the following billing methods to...
» more

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.