DBMS > Amazon Redshift vs. Coveo vs. Datomic vs. Elasticsearch vs. NSDb

System Properties Comparison Amazon Redshift vs. Coveo vs. Datomic vs. Elasticsearch vs. NSDb

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/redshift

www.coveo.com

www.datomic.com

www.elastic.co/elasticsearch

nsdb.io

Technical documentation

docs.aws.amazon.com/redshift

docs.coveo.com

docs.datomic.com

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

nsdb.io/Architecture

Developer

Amazon (based on PostgreSQL)

Coveo

Cognitect

Elastic

Initial release

2012

2010

2017

Current release

1.0.6735, June 2023

8.6, January 2023

License

Commercial or Open Source

commercial

limited edition free

Open Source

Elastic License

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

Java, Clojure

Java

Java, Scala

Server operating systems

hosted

All OS with a Java VM

Linux
macOS

Data scheme

yes

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

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

All search fields are automatically indexed

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

Java API
RESTful HTTP/JSON API

gRPC
HTTP REST
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

Clojure
Java

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

yes

Triggers

yes

By using transaction functions

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

Using Apache Lucene

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

Memcached and Redis integration

User concepts

Access control

fine grained access rights according to SQL-standard

granular access controls, API key management, content filters

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.