DBMS > GraphDB vs. MySQL vs. TigerGraph

System Properties Comparison GraphDB vs. MySQL vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Widely used open source RDBMS

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

Primary database model

Graph DBMS
RDF store

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	2.77
Rank	#98	Overall
	#8	Graph DBMS
	#4	RDF stores

Score	1022.76
Rank	#2	Overall
	#2	Relational DBMS

Score	1.46
Rank	#150	Overall
	#14	Graph DBMS

Website

www.ontotext.com

www.mysql.com

www.tigergraph.com

Technical documentation

graphdb.ontotext.com/documentation

dev.mysql.com/doc

docs.tigergraph.com

Social network pages

Developer

Ontotext

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2000

1995

2017

Current release

10.4, October 2023

9.0.0, July 2024

License

Commercial or Open Source

commercial

Some plugins of GraphDB Workbench are open sourced

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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++

C++

Server operating systems

All OS with a Java VM
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free and OWL/RDFS-schema support; RDF shapes

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, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

SQL

Support of SQL

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

ADO.NET
JDBC
ODBC
Proprietary native API

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

Supported programming languages

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C++
Java

Server-side scripts

Stored procedures

well-defined plugin interfaces; JavaScript server-side extensibility

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Immediate Consistency

Foreign keys

Referential integrity

yes

Constraint checking

yes

not for MyISAM storage engine

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

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

Deploying Ontotext GraphDB on AWS
27 September 2024

GraphDB in Action: Using Semantics To Push The Envelope Of Software Engineering, Machine Learning, and E-Health Domains
11 September 2024

Accelerating End-to-end Knowledge Graph Solutions with Ontotext’s LinkedLifeData Inventory: The Case of Target Discovery
30 August 2024

Using Entity Linking to Turn Your Graph into a Knowledge Graph
23 August 2024

Considerations to Creating a Graph Center of Excellence: 5 Elements to Ensure Success
22 August 2024

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.