DBMS > Amazon DocumentDB vs. Dgraph vs. Faircom EDGE vs. SQLite

System Properties Comparison Amazon DocumentDB vs. Dgraph vs. Faircom EDGE vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Distributed and scalable native Graph DBMS

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

Graph DBMS

Key-value store
Relational DBMS

Relational DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/documentdb

dgraph.io

www.faircom.com/products/faircom-edge

www.sqlite.org

Technical documentation

aws.amazon.com/documentdb/resources

dgraph.io/docs

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

www.sqlite.org/docs.html

Developer

Dgraph Labs, Inc.

FairCom Corporation

Dwayne Richard Hipp

Initial release

2019

2016

1979

2000

Current release

V3, October 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Restricted, free version available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

ANSI C, C++

Server operating systems

hosted

Linux
OS X
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

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL-92 is not fully supported

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

GraphQL query language
gRPC (using protocol buffers) API
HTTP 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

Go
Java
JavaScript (Node.js)
PHP
Python

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

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

yes

.Net, JavaScript, C/C++

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

File partitioning

Customizable business rules for partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Synchronous replication via Raft

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

when using SQL

yes

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

via file-system locks

Durability

Support for making data persistent

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

Access rights for users and roles

Planned for future releases

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.