DBMS > Drizzle vs. PouchDB vs. SQLite vs. STSdb vs. TigerGraph

System Properties Comparison Drizzle vs. PouchDB vs. SQLite vs. STSdb vs. TigerGraph

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.

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

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

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

pouchdb.com

www.sqlite.org

github.com/STSSoft/STSdb4

www.tigergraph.com

Technical documentation

pouchdb.com/guides

www.sqlite.org/docs.html

docs.tigergraph.com

Developer

Drizzle project, originally started by Brian Aker

Apache Software Foundation

Dwayne Richard Hipp

STS Soft SC

Initial release

2008

2012

2000

2011

2017

Current release

7.2.4, September 2012

7.1.1, June 2019

3.46.0 (23 May 2024), May 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Public Domain

Open Source

GPLv2, commercial license available

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

JavaScript

C++

Server operating systems

FreeBSD
Linux
OS X

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Windows

Linux

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.

yes

primitive types and user defined types (classes)

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

via views

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-92 is not fully supported

SQL-like query language (GSQL)

APIs and other access methods

JDBC

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

JavaScript

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

C#
Java

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

by using IndexedDB, WebSQL or LevelDB as backend

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

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.