DBMS > EsgynDB vs. Google Cloud Bigtable vs. IBM Db2 vs. JaguarDB vs. RocksDB

System Properties Comparison EsgynDB vs. Google Cloud Bigtable vs. IBM Db2 vs. JaguarDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Common in IBM host environments, 2 different versions for host and Windows/Linux

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store
Vector DBMS

Key-value store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

Website

www.esgyn.cn

cloud.google.com/bigtable

www.ibm.com/products/db2

www.jaguardb.com

rocksdb.org

Technical documentation

cloud.google.com/bigtable/docs

www.ibm.com/docs/en/db2

www.jaguardb.com/support.html

github.com/facebook/rocksdb/wiki

Developer

Esgyn

Google

IBM

DataJaguar, Inc.

Facebook, Inc.

Initial release

2015

1983

host version

2015

2013

Current release

12.1, October 2016

3.3 July 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

free version is available

Open Source

GPL V3.0

Open Source

BSD

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

C++, Java

C and C++

C++

the server part. Clients available in other languages

C++

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

JDBC
ODBC

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

with separate tools (MQ, InfoSphere)

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

rights management via user accounts

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.