DBMS > Graphite vs. HyperSQL vs. MySQL vs. Tigris

System Properties Comparison Graphite vs. HyperSQL vs. MySQL vs. Tigris

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Widely used open source RDBMS

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	3.23
Rank	#93	Overall
	#48	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

github.com/graphite-project/graphite-web

hsqldb.org

www.mysql.com

www.tigrisdata.com

Technical documentation

graphite.readthedocs.io

hsqldb.org/web/hsqlDocsFrame.html

dev.mysql.com/doc

www.tigrisdata.com/docs

Developer

Chris Davis

Oracle

since 2010, originally MySQL AB, then Sun

Tigris Data, Inc.

Initial release

2006

2001

1995

2022

Current release

2.7.2, June 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

based on BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 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.

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

Implementation language

Python

Java

C and C++

Server operating systems

Linux
Unix

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

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

APIs and other access methods

HTTP API
Sockets

HTTP API

JDBC via HTTP
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC
Java

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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

Java, SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

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

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

yes, using FoundationDB

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and 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.