DBMS > Apache Drill vs. Dgraph vs. FatDB vs. SQLite vs. Yaacomo

System Properties Comparison Apache Drill vs. Dgraph vs. FatDB vs. SQLite vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Distributed and scalable native Graph DBMS

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

Widely used embeddable, in-process RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Relational DBMS

Graph DBMS

Document store
Key-value store

Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

dgraph.io

www.sqlite.org

yaacomo.com

Technical documentation

drill.apache.org/docs

dgraph.io/docs

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Dgraph Labs, Inc.

FatCloud

Dwayne Richard Hipp

Q2WEB GmbH

Initial release

2012

2016

2012

2000

2009

Current release

1.20.3, January 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

Server operating systems

Linux
OS X
Windows

Windows

server-less

Android
Linux
Windows

Data scheme

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

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

SQL SELECT statement is SQL:2003 compliant

Via inetgration in SQL Server

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

C++

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

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

Server-side scripts

Stored procedures

user defined functions

yes

via applications

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

selectable replication factor

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Planned for future releases

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.