DBMS > Brytlyt vs. Graphite vs. MySQL vs. TigerGraph vs. TinkerGraph

System Properties Comparison Brytlyt vs. Graphite vs. MySQL vs. TigerGraph vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used open source RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

brytlyt.io

github.com/graphite-project/graphite-web

www.mysql.com

www.tigergraph.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.brytlyt.io

graphite.readthedocs.io

dev.mysql.com/doc

docs.tigergraph.com

Developer

Brytlyt

Chris Davis

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2006

1995

2017

2009

Current release

5.0, August 2023

8.3.0, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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.

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

Implementation language

C, C++ and CUDA

Python

C and C++

C++

Java

Server operating systems

Linux
OS X
Windows

Linux
Unix

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Sockets

ADO.NET
JDBC
ODBC
Proprietary native API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

TinkerPop 3

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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

C++
Java

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

yes

Relationships in graphs

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

optional

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

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.