DBMS > AnzoGraph DB vs. Apache Impala vs. MySQL vs. Valentina Server

System Properties Comparison AnzoGraph DB vs. Apache Impala vs. MySQL vs. Valentina Server

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

Analytic DBMS for Hadoop

Widely used open source RDBMS

Object-relational database and reports server

Primary database model

Graph DBMS
RDF store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

cambridgesemantics.com/anzograph

impala.apache.org

www.mysql.com

www.valentina-db.net

Technical documentation

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

impala.apache.org/impala-docs.html

dev.mysql.com/doc

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Cambridge Semantics

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Oracle

since 2010, originally MySQL AB, then Sun

Paradigma Software

Initial release

2018

2013

1995

1999

Current release

2.3, January 2021

4.1.0, June 2022

8.4.0, April 2024

5.7.5

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache Version 2

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.

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

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

Schema-free and OWL/RDFS-schema support

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

SQL

Support of SQL

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

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

APIs and other access methods

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

ODBC

Supported programming languages

C++
Java
Python

All languages supporting JDBC/ODBC

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 rights for users, groups and roles

based on Apache Sentry and Kerberos

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.