DBMS > Amazon Redshift vs. atoti vs. Coveo vs. RavenDB vs. SpaceTime

System Properties Comparison Amazon Redshift vs. atoti vs. Coveo vs. RavenDB vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Open Source Operational and Transactional Enterprise NoSQL Document Database

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

aws.amazon.com/redshift

atoti.io

www.coveo.com

ravendb.net

www.mireo.com/spacetime

Technical documentation

docs.aws.amazon.com/redshift

docs.atoti.io

docs.coveo.com

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

ActiveViam

Coveo

Hibernating Rhinos

Mireo

Initial release

2012

2010

2020

Current release

5.4, July 2022

License

Commercial or Open Source

commercial

free versions available

commercial

Open Source

AGPL version 3, commercial license available

commercial

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

C++

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

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

Multidimensional Expressions (MDX)

SQL-like query language (RQL)

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

yes

Sharding

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate 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

yes

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

User concepts

Access control

fine grained access rights according to SQL-standard

granular access controls, API key management, content filters

Authorization levels configured per client per database

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.