DBMS > AnzoGraph DB vs. Apache Phoenix vs. Percona Server for MySQL vs. RocksDB

System Properties Comparison AnzoGraph DB vs. Apache Phoenix vs. Percona Server for MySQL vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

A scale-out RDBMS with evolutionary schema built on Apache HBase

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Graph DBMS
RDF store

Relational DBMS

Key-value store

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

cambridgesemantics.com/anzograph

phoenix.apache.org

www.percona.com/software/mysql-database/percona-server

rocksdb.org

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

phoenix.apache.org

www.percona.com/downloads/Percona-Server-LATEST

github.com/facebook/rocksdb/wiki

Developer

Cambridge Semantics

Apache Software Foundation

Percona

Facebook, Inc.

Initial release

2018

2014

2008

2013

Current release

2.3, January 2021

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

8.0.36-28, 2024

8.11.4, April 2024

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache Version 2.0

Open Source

GPL version 2

Open Source

BSD

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

Linux

Linux
Unix
Windows

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

yes

late-bound, schema-on-read capabilities

yes

schema-free

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

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

JDBC

ADO.NET
JDBC
ODBC

C++ API
Java API

Supported programming languages

C++
Java
Python

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Multi-source replication
Source-replica replication

Multi-source replication
Source-replica replication
XtraDB Cluster

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

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

Access rights for users and roles

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.