DBMS > Apache Drill vs. CouchDB vs. Faircom EDGE vs. SQLite

System Properties Comparison Apache Drill vs. CouchDB vs. Faircom EDGE vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Document store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	0.02
Rank	#370	Overall
	#55	Key-value stores
	#157	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

couchdb.apache.org

www.faircom.com/products/faircom-edge

www.sqlite.org

Technical documentation

drill.apache.org/docs

docs.couchdb.org/en/stable

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

FairCom Corporation

Dwayne Richard Hipp

Initial release

2012

2005

1979

2000

Current release

1.20.3, January 2023

3.3.3, December 2023

V3, October 2020

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

commercial

Restricted, free version available

Open Source

Public Domain

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

Erlang

ANSI C, C++

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Android
Linux

ARM, x86
Raspbian
Windows

server-less

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

yes

not rigid because of 'dynamic typing' concept.

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

ANSI SQL queries

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

View functions in JavaScript

yes

.Net, JavaScript, C/C++

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

File partitioning

Customizable business rules for partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

across SQL and NoSQL

yes

via file-system locks

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

Access rights for users can be defined per database

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.