DBMS > 4D vs. JanusGraph vs. Memcached vs. MySQL

System Properties Comparison 4D vs. JanusGraph vs. Memcached vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A Graph DBMS optimized for distributed clusters

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

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	2.37
Rank	#110	Overall
	#54	Relational DBMS

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	16.84
Rank	#32	Overall
	#4	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

developer.4d.com

docs.janusgraph.org

github.com/memcached/memcached/wiki

dev.mysql.com/doc

Developer

4D, Inc

Linux Foundation; originally developed as Titan by Aurelius

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1984

2017

2003

1995

Current release

v20, April 2023

1.0.0, October 2023

1.6.29, June 2024

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

C and C++

Server operating systems

OS X
Windows

Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

with proprietary extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

4D proprietary IDE
PHP

Clojure
Java
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
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

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)

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

Repcached, a Memcached patch, provides this functionallity

Multi-source 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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users and groups

User authentification and security via Rexster Graph Server

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

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.