DBMS > EJDB vs. Hypertable vs. Oracle vs. OrigoDB vs. PostGIS

System Properties Comparison EJDB vs. Hypertable vs. Oracle vs. OrigoDB vs. PostGIS

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

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

An open source BigTable implementation based on distributed file systems such as Hadoop

Widely used RDBMS

A fully ACID in-memory object graph database

Spatial extension of PostgreSQL

Primary database model

Document store

Wide column store

Relational DBMS

Document store
Object oriented DBMS

Spatial DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

github.com/Softmotions/ejdb

www.oracle.com/database

origodb.com

postgis.net

Technical documentation

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

docs.oracle.com/en/database

origodb.com/docs

postgis.net/documentation

Developer

Softmotions

Hypertable Inc.

Oracle

Robert Friberg et al

Initial release

2012

2009

1980

2009

under the name LiveDB

2005

Current release

0.9.8.11, March 2016

23c, September 2023

3.4.2, February 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GNU version 3. Commercial license available

commercial

restricted free version is available

Open Source

GPL v2.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

C++

C and C++

Server operating systems

server-less

Linux
OS X
Windows

an inofficial Windows port is available

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

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.

yes

can be achieved using .NET

yes

Secondary indexes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

in-process shared library

C++ API
Thrift

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

Supported programming languages

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

C++
Java
Perl
PHP
Python
Ruby

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

user defined functions

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Sharding, horizontal partitioning

horizontal partitioning

client side managed; servers are not synchronized

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor on file system level

Multi-source replication
Source-replica replication

Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

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

isolation level can be parameterized

ACID

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 capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

yes

based on PostgreSQL

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.