DBMS > EsgynDB vs. Infobright vs. Postgres-XL vs. Vitess

System Properties Comparison EsgynDB vs. Infobright vs. Postgres-XL vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Secondary database models

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	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.esgyn.cn

ignitetech.com/softwarelibrary/infobrightdb

www.postgres-xl.org

vitess.io

Technical documentation

www.postgres-xl.org/documentation

vitess.io/docs

Developer

Esgyn

Ignite Technologies Inc.; formerly InfoBright Inc.

The Linux Foundation, PlanetScale

Initial release

2015

2005

2014

since 2012, originally named StormDB

2013

Current release

10 R1, October 2018

15.0.2, December 2022

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Mozilla public license

Open Source

Apache Version 2.0, commercial licenses available

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.

Implementation language

C++, Java

Server operating systems

Linux

Linux
Windows

Linux
macOS

Docker
Linux
macOS

Data scheme

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

XML type, but no XML query functionality

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

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

MVCC

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

exploiting MySQL or PostgreSQL frontend capabilities

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Ignite Buys Database Vendor Infobright
2 May 2017, Datanami

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page