DBMS > Amazon Redshift vs. Elasticsearch vs. Manticore Search vs. NSDb vs. SiteWhere

System Properties Comparison Amazon Redshift vs. Elasticsearch vs. Manticore Search vs. NSDb vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Multi-storage database for search, including full-text search.

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

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Search engine

Time Series DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Time Series DBMS

using the Manticore Columnar Library

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	128.79
Rank	#8	Overall
	#1	Search engines

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

aws.amazon.com/redshift

www.elastic.co/elasticsearch

manticoresearch.com

nsdb.io

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

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

manual.manticoresearch.com

nsdb.io/Architecture

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Elastic

Manticore Software

SiteWhere

Initial release

2012

2010

2017

2010

Current release

8.6, January 2023

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

Open Source

GPL version 2

Open Source

Apache Version 2.0

Open Source

Common Public Attribution License Version 1.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

C++

Java, Scala

Java

Server operating systems

hosted

All OS with a Java VM

FreeBSD
Linux
macOS
Windows

Linux
macOS

Linux
OS X
Windows

Data scheme

yes

schema-free

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

Fixed schema

predefined scheme

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes: int, bigint, decimal, string

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.

Can index from XML

Secondary indexes

restricted

yes

All search fields are automatically indexed

yes

full-text index on all search fields

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

Java API
RESTful HTTP/JSON API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

gRPC
HTTP REST
WebSocket

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Java
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

selectable replication factor

based on HBase

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

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

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

Using Apache Lucene

yes

In-memory capabilities

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

yes

Memcached and Redis integration

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.