DBMS > Graph Engine vs. IBM Db2 warehouse vs. InfinityDB vs. MySQL

System Properties Comparison Graph Engine vs. IBM Db2 warehouse vs. InfinityDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Cloud-based data warehousing service

A Java embedded Key-Value Store which extends the Java Map interface

Widely used open source RDBMS

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.26
Rank	#162	Overall
	#73	Relational DBMS

Score	0.00
Rank	#383	Overall
	#59	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.graphengine.io

www.ibm.com/products/db2/warehouse

boilerbay.com

www.mysql.com

Technical documentation

www.graphengine.io/docs/manual

boilerbay.com/infinitydb/manual

dev.mysql.com/doc

Developer

Microsoft

IBM

Boiler Bay Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2010

2014

2002

1995

Current release

4.0

9.0.0, July 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

.NET and C

Java

C and C++

Server operating systems

.NET

hosted

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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.

Import/export of XML data possible

yes

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

.NET Client API
JDBC
ODBC
OLE DB

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
F#
Visual Basic

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Java

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

Server-side scripts

Stored procedures

yes

PL/SQL, SQL PL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

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.