DBMS > Kinetica vs. MySQL vs. SpatiaLite vs. TimesTen

System Properties Comparison Kinetica vs. MySQL vs. SpatiaLite vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

Widely used open source RDBMS

Spatial extension of SQLite

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	0.42
Rank	#261	Overall
	#120	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

www.kinetica.com

www.mysql.com

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

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.kinetica.com

dev.mysql.com/doc

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

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

Kinetica

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

1995

2008

1998

Current release

7.1, August 2021

9.0.0, July 2024

5.0.0, August 2020

Release 22.1

License

Commercial or Open Source

commercial

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

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.

Implementation language

C, C++

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

server-less

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

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

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

C++
Java
JavaScript (Node.js)
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++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

PL/SQL

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

by means of logfiles and checkpoints

In-memory capabilities

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

yes

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users and roles on table level

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.