DBMS > Drizzle vs. FatDB vs. SpatiaLite vs. SQLite vs. TimescaleDB

System Properties Comparison Drizzle vs. FatDB vs. SpatiaLite vs. SQLite vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial extension of SQLite

Widely used embeddable, in-process RDBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Document store
Key-value store

Spatial DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

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

www.sqlite.org

www.timescale.com

Technical documentation

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

www.sqlite.org/docs.html

docs.timescale.com

Developer

Drizzle project, originally started by Brian Aker

FatCloud

Alessandro Furieri

Dwayne Richard Hipp

Timescale

Initial release

2008

2012

2008

2000

2017

Current release

7.2.4, September 2012

5.0.0, August 2020

3.46.0 (23 May 2024), May 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

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

Open Source

Public Domain

Open Source

Apache 2.0

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

Server operating systems

FreeBSD
Linux
OS X

Windows

server-less

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

Via inetgration in SQL Server

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C
C++
Java
PHP

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

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.