DBMS > FatDB vs. LevelDB vs. OrientDB vs. SQLite vs. TerminusDB

System Properties Comparison FatDB vs. LevelDB vs. OrientDB vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

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

Description

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

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

Primary database model

Document store
Key-value store

Key-value store

Document store
Graph DBMS
Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

github.com/google/leveldb

orientdb.org

www.sqlite.org

terminusdb.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

FatCloud

Google

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2012

2011

2010

2000

2018

Current release

1.23, February 2021

3.2.29, March 2024

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

Apache version 2

Open Source

Public Domain

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

Java

Prolog, Rust

Server operating systems

Windows

Illumos
Linux
OS X
Windows

All OS with a Java JDK (>= JDK 6)

server-less

Linux

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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

Via inetgration in SQL Server

SQL-like query language, no joins

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

via applications

Java, Javascript

yes

Triggers

yes

via applications

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

with automatic compression on writes

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

Can implement custom security layer via applications

Access rights for users and roles; record level security configurable

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.