DBMS > Kingbase vs. RavenDB vs. RDF4J vs. RocksDB

System Properties Comparison Kingbase vs. RavenDB vs. RDF4J vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

ravendb.net/docs

rdf4j.org/documentation

github.com/facebook/rocksdb/wiki

Developer

BeiJing KINGBASE Information technologies inc.

Hibernating Rhinos

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

Facebook, Inc.

Initial release

1999

2010

2004

2013

Current release

V8.0, August 2021

5.4, July 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

BSD

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 Java

Java

C++

Server operating systems

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

Linux

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

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

Standard with numerous extensions

SQL-like query language (RQL)

APIs and other access methods

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

C++ API
Java API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

ACID, Cluster-wide transaction available

ACID

Isolation support depends on the API used

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

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

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.