DBMS > EJDB vs. Fauna vs. Linter vs. RocksDB vs. Warp 10

System Properties Comparison EJDB vs. Fauna vs. Linter vs. RocksDB vs. Warp 10

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.

RDBMS for high security requirements

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Spatial 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.09
Rank	#346	Overall
	#152	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

github.com/Softmotions/ejdb

Technical documentation

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

docs.fauna.com

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Softmotions

Fauna, Inc.

relex.ru

Facebook, Inc.

SenX

Initial release

2012

2014

1990

2013

2015

Current release

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

BSD

Open Source

Apache License 2.0

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

C and C++

C++

Java

Server operating systems

server-less

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

yes

APIs and other access methods

in-process shared library

RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

C++ API
Java API

HTTP API
Jupyter
WebSocket

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

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

consistent hashing

none

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

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

Identity management, authentication, and access control

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.