DBMS > Graphite vs. MySQL vs. Oracle Coherence vs. TerminusDB

System Properties Comparison Graphite vs. MySQL vs. Oracle Coherence vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used open source RDBMS

Oracles in-memory data grid solution

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

github.com/graphite-project/graphite-web

www.mysql.com

www.oracle.com/java/coherence

terminusdb.com

Technical documentation

graphite.readthedocs.io

dev.mysql.com/doc

docs.oracle.com/en/middleware/standalone/coherence

terminusdb.github.io/terminusdb/#

Developer

Chris Davis

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

DataChemist Ltd.

Initial release

2006

1995

2007

2018

Current release

8.4.0, April 2024

14.1, August 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL V3

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

Python

C and C++

Java

Prolog, Rust

Server operating systems

Linux
Unix

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

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

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

HTTP API
Sockets

ADO.NET
JDBC
ODBC
Proprietary native API

JCache
JPA
RESTful HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

JavaScript (Node.js)
Python

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

.Net
C++
Java

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes, with selectable consistency level

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

optionally

yes

in-memory journaling

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 with fine-grained authorization concept

no user groups or roles

authentification to access the cache via certificates or http basic authentication

Role-based access control

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.