DBMS > Oracle vs. RavenDB vs. XTDB

System Properties Comparison Oracle vs. RavenDB vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store

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	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

www.oracle.com/database

ravendb.net

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.oracle.com/en/database

ravendb.net/docs

www.xtdb.com/docs

Developer

Oracle

Hibernating Rhinos

Juxt Ltd.

Initial release

1980

2010

2019

Current release

23c, September 2023

5.4, July 2022

1.19, September 2021

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

Open Source

MIT 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

C and C++

Clojure

Server operating systems

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

Linux
macOS
Raspberry Pi
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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)

limited SQL, making use of Apache Calcite

APIs and other access methods

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

HTTP REST
JDBC

Supported programming languages

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

Clojure
Java

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes, each node contains all data

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.

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.