DBMS > gStore vs. JaguarDB vs. RavenDB vs. VoltDB

System Properties Comparison gStore vs. JaguarDB vs. RavenDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native Graph DBMS to store and maintain very large RDF datasets.

Performant, highly scalable DBMS for AI and IoT applications

Open Source Operational and Transactional Enterprise NoSQL Document Database

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Graph DBMS
RDF store

Key-value store
Vector DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.04
Rank	#359	Overall
	#37	Graph DBMS
	#18	RDF stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

en.gstore.cn/#/enDocs

www.jaguardb.com/support.html

ravendb.net/docs

docs.voltdb.com

Developer

DataJaguar, Inc.

Hibernating Rhinos

VoltDB Inc.

Initial release

2016

2015

2010

Current release

1.2, November 2023

3.3 July 2023

5.4, July 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

GPL V3.0

Open Source

AGPL version 3, commercial license available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++

the server part. Clients available in other languages

Java, C++

Server operating systems

Linux

Linux
macOS
Raspberry Pi
Windows

Linux
OS X

for development

Data scheme

schema-free and OWL/RDFS-schema support

yes

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.

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language (RQL)

yes

only a subset of SQL 99

APIs and other access methods

HTTP API
SPARQL 1.1

JDBC
ODBC

.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
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID, Cluster-wide transaction available

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

Users, roles and permissions, Role-Based Access Control (RBAC) supported

rights management via user accounts

Authorization levels configured per client per database

Users and roles with access to stored procedures

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

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

provided by Google News

Share this page