DBMS > EsgynDB vs. Google BigQuery vs. Immudb vs. Netezza vs. Vitess

System Properties Comparison EsgynDB vs. Google BigQuery vs. Immudb vs. Netezza vs. Vitess

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Data warehouse and analytics appliance part of IBM PureSystems

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.esgyn.cn

cloud.google.com/bigquery

github.com/codenotary/immudb
immudb.io

www.ibm.com/products/netezza

vitess.io

Technical documentation

cloud.google.com/bigquery/docs

docs.immudb.io

vitess.io/docs

Developer

Esgyn

Google

Codenotary

IBM

The Linux Foundation, PlanetScale

Initial release

2015

2010

2020

2000

2013

Current release

1.2.3, April 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2.0, commercial licenses 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

C++, Java

Server operating systems

Linux

hosted

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux

included in appliance

Docker
Linux
macOS

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like syntax

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

gRPC protocol
PostgreSQL wire protocol

JDBC
ODBC
OLE DB

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

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

Java Stored Procedures

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

ACID at shard level

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

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.