DBMS > BigObject vs. Cubrid vs. Ehcache vs. JanusGraph

System Properties Comparison BigObject vs. Cubrid vs. Ehcache vs. JanusGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

A widely adopted Java cache with tiered storage options

A Graph DBMS optimized for distributed clusters

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key-value store

Graph DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Website

bigobject.io

cubrid.com (korean)
cubrid.org (english)

www.ehcache.org

janusgraph.org

Technical documentation

docs.bigobject.io

cubrid.org/manuals

www.ehcache.org/documentation

docs.janusgraph.org

Developer

BigObject, Inc.

CUBRID Corporation, CUBRID Foundation

Terracotta Inc, owned by Software AG

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2015

2008

2009

2017

Current release

11.0, January 2021

3.10.0, March 2022

0.6.3, February 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.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, C++, Java

Java

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
Windows

All OS with a Java VM

Linux
OS X
Unix
Windows

Data scheme

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

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

JCache

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

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

Java

Clojure
Java
Python

Server-side scripts

Stored procedures

Lua

Java Stored Procedures

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

yes

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

by using Terracotta Server

yes

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

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Relationships in graphs

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

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

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

User authentification and security via Rexster Graph Server

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

Jira Data Center user? Here's a critical Ehcache vulnerability to spoil your day
22 July 2021, The Register

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

provided by Google News

Simple Deployment of a Graph Database: JanusGraph | by Edward Elson Kosasih
12 October 2020, Towards Data Science

Database Deep Dives: JanusGraph
8 August 2019, IBM

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

Compose for JanusGraph arrives on Bluemix
15 September 2017, IBM

provided by Google News

Share this page