DBMS > EJDB vs. FatDB vs. OrigoDB vs. RDF4J

System Properties Comparison EJDB vs. FatDB vs. OrigoDB vs. RDF4J

Please select another system to include it in the comparison.

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.

Description

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

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

A fully ACID in-memory object graph database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Document store

Document store
Key-value store

Document store
Object oriented DBMS

RDF store

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Website

github.com/Softmotions/ejdb

origodb.com

rdf4j.org

Technical documentation

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

origodb.com/docs

rdf4j.org/documentation

Developer

Softmotions

FatCloud

Robert Friberg et al

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2012

2009

under the name LiveDB

2004

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Java

Server operating systems

server-less

Windows

Linux
Windows

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

in-process shared library

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

.NET Client API
HTTP API
LINQ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

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

.Net

Java
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

depending on model

Transaction concepts

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

in-memory storage is supported as well

In-memory capabilities

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

yes

User concepts

Access control

Can implement custom security layer via applications

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

Share this page