DBMS > Amazon Redshift vs. Apache Druid vs. dBASE vs. EsgynDB vs. STSdb

System Properties Comparison Amazon Redshift vs. Apache Druid vs. dBASE vs. EsgynDB vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

aws.amazon.com/redshift

druid.apache.org

www.dbase.com

www.esgyn.cn

github.com/STSSoft/STSdb4

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

www.dbase.com/support/knowledgebase

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Asthon Tate

Esgyn

STS Soft SC

Initial release

2012

1979

2015

2011

Current release

29.0.1, April 2024

dBASE 2019, 2019

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

GPLv2, commercial license 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

Java

C++, Java

Server operating systems

hosted

Linux
OS X
Unix

DOS

dBase Classic
Windows

dBase Pro

Linux

Windows

Data scheme

yes

schema-less columns are supported

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

yes

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC

.NET Client API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

dBase proprietary IDE

All languages supporting JDBC/ODBC/ADO.Net

C#
Java

Server-side scripts

Stored procedures

user defined functions

in Python

The IDE can access stored procedures in other database systems.

Java Stored Procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

not for dBase internal data, but IDE does support transactions when accessing external DBMS

ACID

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users and roles

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.