DBMS > Amazon Redshift vs. CockroachDB vs. GeoMesa vs. SAP Advantage Database Server vs. Warp 10

System Properties Comparison Amazon Redshift vs. CockroachDB vs. GeoMesa vs. SAP Advantage Database Server vs. Warp 10

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

www.cockroachlabs.com

www.geomesa.org

www.sap.com/products/advantage-database-server.html

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

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

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Cockroach Labs

CCRi and others

Sybase, SAP

SenX

Initial release

2012

2015

2014

1993

2015

Current release

24.1.0, May 2024

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

Apache License 2.0

commercial

Open Source

Apache License 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

Java

Server operating systems

hosted

Linux
macOS
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

dynamic schema

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

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

JDBC
ODBC

JDBC

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

Delphi
Perl
PHP

Server-side scripts

Stored procedures

user defined functions

in Python

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

depending on storage layer

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

depending on storage layer

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

selectable replication factor

based on HBase

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

based on HBase

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

caching of (temporary) tables can be configured

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.