DBMS > Drizzle vs. Faircom DB vs. SQLite vs. SurrealDB

System Properties Comparison Drizzle vs. Faircom DB vs. SQLite vs. SurrealDB

Please select another system to include it in the comparison.

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.

Description

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Widely used embeddable, in-process RDBMS

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Document store
Graph DBMS

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

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	1.11
Rank	#174	Overall
	#30	Document stores
	#17	Graph DBMS

Website

www.faircom.com/products/faircom-db

www.sqlite.org

surrealdb.com

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.sqlite.org/docs.html

surrealdb.com/docs

Developer

Drizzle project, originally started by Brian Aker

FairCom Corporation

Dwayne Richard Hipp

SurrealDB Ltd

Initial release

2008

1979

2000

2022

Current release

7.2.4, September 2012

V13, July 2024

3.46.1 (13 August 2024), August 2024

v1.5.0, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Restricted, free version available

Open Source

Public Domain

Open Source

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

ANSI C, C++

Rust

Server operating systems

FreeBSD
Linux
OS X

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

server-less

Linux
macOS
Windows

Data scheme

yes

schema free, schema optional, schema required, partial schema,

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes, ANSI SQL with proprietary extensions

yes

SQL-92 is not fully supported

SQL-like query language

APIs and other access methods

JDBC

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

C
C++
Java
PHP

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

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

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

yes, based on authentication and database rules

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.