DBMS > Amazon Redshift vs. dBASE vs. mSQL vs. OrigoDB vs. SiteWhere

System Properties Comparison Amazon Redshift vs. dBASE vs. mSQL vs. OrigoDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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.

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

aws.amazon.com/redshift

www.dbase.com

hughestech.com.au/products/msql

origodb.com

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

www.dbase.com/support/knowledgebase

origodb.com/docs

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Asthon Tate

Hughes Technologies

Robert Friberg et al

SiteWhere

Initial release

2012

1979

1994

2009

under the name LiveDB

2010

Current release

dBASE 2019, 2019

4.4, October 2021

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

Common Public Attribution License Version 1.0

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

Server operating systems

hosted

DOS

dBase Classic
Windows

dBase Pro

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

predefined scheme

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC

none

The IDE can access other DBMS or ODBC-sources.

JDBC
ODBC

.NET Client API
HTTP API
LINQ

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

dBase proprietary IDE

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

The IDE can access stored procedures in other database systems.

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

depending on model

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

Write ahead log

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 and roles

Role based authorization

Users with fine-grained authorization concept

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.