DBMS > AgensGraph vs. Apache Drill vs. MySQL vs. Transwarp Hippo

System Properties Comparison AgensGraph vs. Apache Drill vs. MySQL vs. Transwarp Hippo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Widely used open source RDBMS

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Graph DBMS
Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.05
Rank	#386	Overall
	#15	Vector DBMS

Website

bitnine.net/agensgraph

drill.apache.org

www.mysql.com

www.transwarp.cn/en/subproduct/hippo

Technical documentation

bitnine.net/documentation

drill.apache.org/docs

dev.mysql.com/doc

Developer

Bitnine Global Inc.

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2012

1995

2023

Current release

2.1, December 2018

1.20.3, January 2023

8.4.0, April 2024

1.0, May 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

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

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

depending on used data model

schema-free

yes

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

C
Java
JavaScript
Python

C++

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

C++
Java
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica 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

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

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

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Users with fine-grained authorization concept

no user groups or roles

Role based access control and fine grained access rights

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.