DBMS > Drizzle vs. FatDB vs. JaguarDB vs. STSdb vs. TerminusDB

System Properties Comparison Drizzle vs. FatDB vs. JaguarDB vs. STSdb vs. TerminusDB

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.

Performant, highly scalable DBMS for AI and IoT applications

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store
Vector DBMS

Key-value store

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.jaguardb.com

github.com/STSSoft/STSdb4

terminusdb.com

Technical documentation

www.jaguardb.com/support.html

terminusdb.github.io/terminusdb/#

Developer

Drizzle project, originally started by Brian Aker

FatCloud

DataJaguar, Inc.

STS Soft SC

DataChemist Ltd.

Initial release

2008

2012

2015

2011

2018

Current release

7.2.4, September 2012

3.3 July 2023

4.0.8, September 2015

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

GPL V3.0

Open Source

GPLv2, commercial license available

Open Source

GPL V3

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

the server part. Clients available in other languages

Prolog, Rust

Server operating systems

FreeBSD
Linux
OS X

Windows

Linux

Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

with proprietary extensions

Via inetgration in SQL Server

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language (WOQL)

APIs and other access methods

JDBC

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

JDBC
ODBC

.NET Client API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C++
Java
PHP

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C#
Java

JavaScript
Python

Server-side scripts

Stored procedures

yes

via applications

yes

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Multi-source replication

none

Journaling Streams

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

Eventual 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

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.

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

rights management via user accounts

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Dublin-based data collaboration tool TerminusDB raises €3.6 million in seed round
15 March 2021, Tech.eu

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

provided by Google News

Share this page