DBMS > AgensGraph vs. Drizzle vs. RavenDB vs. YottaDB

System Properties Comparison AgensGraph vs. Drizzle vs. RavenDB vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Open Source Operational and Transactional Enterprise NoSQL Document Database

A fast and solid embedded Key-value store

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Document store

Key-value store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS

using the Octo plugin

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

bitnine.net/agensgraph

ravendb.net

yottadb.com

Technical documentation

bitnine.net/documentation

ravendb.net/docs

yottadb.com/resources/documentation

Developer

Bitnine Global Inc.

Drizzle project, originally started by Brian Aker

Hibernating Rhinos

YottaDB, LLC

Initial release

2016

2008

2010

2001

Current release

2.1, December 2018

7.2.4, September 2012

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GNU GPL

Open Source

AGPL version 3, commercial license available

Open Source

AGPL 3.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++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux
macOS
Raspberry Pi
Windows

Docker
Linux

Data scheme

depending on used data model

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (RQL)

by using the Octo plugin

APIs and other access methods

Cypher Query Language
JDBC

JDBC

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

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
Java
JavaScript
Python

C
C++
Java
PHP

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Authorization levels configured per client per database

Users and groups based on OS-security mechanisms

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

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Graph DBMS Performance Comparison AgensGraph vs. Neo4j
29 June 2017, Business Wire

Bitnine Releases AgensGraph 2.1, the Multi-model Graph Database Optimized for the Legacy Environment
29 January 2019, Business Wire

Bitnine: The Newly Revealed 'AI Teacher' Powered by Graph Database Delivers Hyper-Personalized Learning ...
25 March 2019, Business Wire

Bitnine Announces Plans for New Business with Apache AGE's Top-Level Promotion
14 June 2022, Business Wire

provided by Google 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

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

RavenDB Adds Graph Queries
15 May 2019, Datanami

provided by Google News

Share this page