DBMS > Amazon Redshift vs. Derby vs. GeoMesa vs. LokiJS

System Properties Comparison Amazon Redshift vs. Derby vs. GeoMesa vs. LokiJS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

In-memory JavaScript DBMS

Primary database model

Relational DBMS

Spatial DBMS

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Website

aws.amazon.com/redshift

db.apache.org/derby

www.geomesa.org

github.com/techfort/LokiJS

Technical documentation

docs.aws.amazon.com/redshift

db.apache.org/derby/manuals/index.html

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

techfort.github.io/LokiJS

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

CCRi and others

Initial release

2012

1997

2014

Current release

10.17.1.0, November 2023

4.0.5, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache License 2.0

Open Source

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

Scala

JavaScript

Server operating systems

hosted

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

yes

schema-free

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

Secondary indexes

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

JDBC

JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

Java

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

none

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

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

yes

depending on the DBMS used for storage

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.