DBMS > MySQL vs. SpatiaLite vs. TDSQL for MySQL vs. TerminusDB

System Properties Comparison MySQL vs. SpatiaLite vs. TDSQL for MySQL vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Spatial extension of SQLite

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

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

Spatial DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

Document store
Spatial DBMS

Document store
RDF store

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Score	0.96
Rank	#192	Overall
	#88	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

www.tencentcloud.com/products/dcdb

terminusdb.com

Technical documentation

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.tencentcloud.com/document/product/1042

terminusdb.github.io/terminusdb/#

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Tencent

DataChemist Ltd.

Initial release

1995

2008

2013

2018

Current release

9.0.0, July 2024

5.0.0, August 2020

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

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.

Implementation language

C and C++

C++

Prolog, Rust

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

server-less

hosted

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

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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++
Java
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Automatic sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

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

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

Role-based access control

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.