DBMS > Apache Drill vs. Atos Standard Common Repository vs. EsgynDB vs. HyperSQL vs. Postgres-XL

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. EsgynDB vs. HyperSQL vs. Postgres-XL

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

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

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

drill.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.esgyn.cn

hsqldb.org

www.postgres-xl.org

Technical documentation

drill.apache.org/docs

hsqldb.org/web/hsqlDocsFrame.html

www.postgres-xl.org/documentation

Developer

Apache Software Foundation

Atos Convergence Creators

Esgyn

Initial release

2012

2016

2015

2001

2014

since 2012, originally named StormDB

Current release

1.20.3, January 2023

1703

2.7.2, June 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

based on BSD license

Open Source

Mozilla public license

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

Java

C++, Java

Java

Server operating systems

Linux
OS X
Windows

Linux

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Linux
macOS

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

ADO.NET
JDBC
ODBC

HTTP API

JDBC via HTTP
JDBC
ODBC

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

Supported programming languages

C++

All languages with LDAP bindings

All languages supporting JDBC/ODBC/ADO.Net

All languages supporting JDBC/ODBC
Java

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

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Java, SQL

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Depending on the underlying data source

LDAP bind authentication

fine grained access rights according to SQL-standard

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

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill improves big data SQL query engine
31 August 2021, TechTarget

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

provided by Google News

HyperSQL DataBase flaw leaves library vulnerable to RCE
24 October 2022, The Daily Swig

Introduction to JDBC with HSQLDB tutorial
14 November 2022, TheServerSide.com

provided by Google News

Share this page