DBMS > Amazon Redshift vs. GeoMesa vs. LevelDB vs. Sqrrl vs. Tkrzw

System Properties Comparison Amazon Redshift vs. GeoMesa vs. LevelDB vs. Sqrrl vs. Tkrzw

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Adaptable, secure NoSQL built on Apache Accumulo

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

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	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

www.geomesa.org

github.com/google/leveldb

sqrrl.com

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

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

github.com/google/leveldb/blob/main/doc/index.md

Developer

Amazon (based on PostgreSQL)

CCRi and others

Google

Amazon

originally Sqrrl Data, Inc.

Mikio Hirabayashi

Initial release

2012

2014

2011

2012

2020

Current release

4.0.5, February 2024

1.23, February 2021

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

BSD

commercial

Open Source

Apache Version 2.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

Scala

C++

Java

C++

Server operating systems

hosted

Illumos
Linux
OS X
Windows

Linux

Linux
macOS

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Sharding

making use of Hadoop

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

none

selectable replication factor

making use of Hadoop

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

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.