DBMS > Graph Engine vs. Oracle vs. RavenDB vs. Transbase

System Properties Comparison Graph Engine vs. Oracle vs. RavenDB vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Widely used RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Document store

Relational 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

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.graphengine.io

www.oracle.com/database

ravendb.net

www.transaction.de/en/products/transbase.html

Technical documentation

www.graphengine.io/docs/manual

docs.oracle.com/en/database

ravendb.net/docs

www.transaction.de/en/products/transbase/features.html

Developer

Microsoft

Oracle

Hibernating Rhinos

Transaction Software GmbH

Initial release

2010

1980

2010

1987

Current release

23c, September 2023

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

commercial

free development license

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

.NET and C

C and C++

Server operating systems

.NET

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

Linux
macOS
Raspberry Pi
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

Schemaless in JSON and XML columns

schema-free

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (RQL)

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
F#
Visual Basic

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
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID, Cluster-wide transaction available

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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'

User concepts

Access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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.