DBMS > Amazon Redshift vs. GeoSpock vs. LevelDB vs. Sequoiadb

System Properties Comparison Amazon Redshift vs. GeoSpock vs. LevelDB vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Spatial and temporal data processing engine for extreme data scale

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

NewSQL database with distributed OLTP and SQL

Primary database model

Relational DBMS

Key-value store

Document store
Relational DBMS

Secondary database models

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

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

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

aws.amazon.com/redshift

geospock.com

github.com/google/leveldb

www.sequoiadb.com

Technical documentation

docs.aws.amazon.com/redshift

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

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Amazon (based on PostgreSQL)

GeoSpock

Google

Sequoiadb Ltd.

Initial release

2012

2011

2013

Current release

2.0, September 2019

1.23, February 2021

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

Server: AGPL; Client: Apache V2

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, Javascript

C++

Server operating systems

hosted

Illumos
Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

temporal, categorical

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC

proprietary protocol using JSON

Supported programming languages

All languages supporting JDBC/ODBC

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

Document is locked during a transaction

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

simple password-based access control

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.