DBMS > EJDB vs. Fauna vs. OrigoDB vs. SQLite

System Properties Comparison EJDB vs. Fauna vs. OrigoDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

A fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.52
Rank	#153	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/Softmotions/ejdb

fauna.com

origodb.com

www.sqlite.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.fauna.com

origodb.com/docs

www.sqlite.org/docs.html

Developer

Softmotions

Fauna, Inc.

Robert Friberg et al

Dwayne Richard Hipp

Initial release

2012

2014

2009

under the name LiveDB

2000

Current release

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

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

Scala

Server operating systems

server-less

hosted

Linux
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

in-process shared library

RESTful HTTP API

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

.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

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

consistent hashing

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

via file-system locks

Durability

Support for making data persistent

yes

Write ahead log

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

Identity management, authentication, and access control

Role based authorization

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.