DBMS > BigObject vs. EJDB vs. Infobright vs. RDF4J

System Properties Comparison BigObject vs. EJDB vs. Infobright vs. RDF4J

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Relational DBMS

RDF store

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

bigobject.io

github.com/Softmotions/ejdb

ignitetech.com/softwarelibrary/infobrightdb

rdf4j.org

Technical documentation

docs.bigobject.io

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

rdf4j.org/documentation

Developer

BigObject, Inc.

Softmotions

Ignite Technologies Inc.; formerly InfoBright Inc.

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

Initial release

2015

2012

2005

2004

License

Commercial or Open Source

commercial

free community edition available

Open Source

GPLv2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

server-less

Linux
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

in-process shared library

ADO.NET
JDBC
ODBC

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
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
PHP
Python

Server-side scripts

Stored procedures

Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

typically not needed, however similar functionality with collection joins possible

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 lock on objects (tables, trees)

yes

Read/Write Locking

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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