DBMS > Amazon Redshift vs. dBASE vs. GeoMesa vs. RDF4J vs. Solr

System Properties Comparison Amazon Redshift vs. dBASE vs. GeoMesa vs. RDF4J vs. Solr

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.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Secondary database models

Spatial 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	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

www.dbase.com/support/knowledgebase

www.geomesa.org/documentation/stable/user/index.html

rdf4j.org/documentation

solr.apache.org/resources.html

Developer

Amazon (based on PostgreSQL)

Asthon Tate

CCRi and others

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Apache Software Foundation

Initial release

2012

1979

2014

2004

2006

Current release

dBASE 2019, 2019

5.0.0, May 2024

9.6.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache Version 2

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

Scala

Java

Server operating systems

hosted

DOS

dBase Classic
Windows

dBase Pro

Linux
OS X
Unix
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

RDF Schemas

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

Secondary indexes

restricted

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC

none

The IDE can access other DBMS or ODBC-sources.

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

dBase proprietary IDE

Java
PHP
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

The IDE can access stored procedures in other database systems.

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual 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

Isolation support depends on the API used

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

yes

depending on the DBMS used for storage

yes

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.