DBMS > BigObject vs. JanusGraph vs. MonetDB vs. MySQL vs. Yaacomo

System Properties Comparison BigObject vs. JanusGraph vs. MonetDB vs. MySQL vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Analytic DBMS for real-time computations and queries

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

A relational database management system that stores data in columns

Widely used open source RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

yaacomo.com

Technical documentation

docs.bigobject.io

docs.janusgraph.org

www.monetdb.org/Documentation

dev.mysql.com/doc

Developer

BigObject, Inc.

Linux Foundation; originally developed as Titan by Aurelius

MonetDB BV

Oracle

since 2010, originally MySQL AB, then Sun

Q2WEB GmbH

Initial release

2015

2017

2004

1995

2009

Current release

0.6.3, February 2023

Dec2023 (11.49), December 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache 2.0

Open Source

Mozilla Public License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Android
Linux
Windows

Data scheme

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

SQL-like DML and DDL statements

yes

SQL 2003 with some extensions

yes

with proprietary extensions

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

Clojure
Java
Python

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Lua

yes

yes, in SQL, C, R

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding via remote tables

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Source-replica replication available in experimental status

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Relationships in graphs

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.