DBMS > Amazon Redshift vs. Elasticsearch vs. Faircom EDGE

System Properties Comparison Amazon Redshift vs. Elasticsearch vs. Faircom EDGE

Please select another system to include it in the comparison.

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

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Primary database model

Relational DBMS

Search engine

Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	0.03
Rank	#380	Overall
	#59	Key-value stores
	#157	Relational DBMS

Website

aws.amazon.com/redshift

www.elastic.co/elasticsearch

www.faircom.com/products/faircom-edge

Technical documentation

docs.aws.amazon.com/redshift

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

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

Developer

Amazon (based on PostgreSQL)

Elastic

FairCom Corporation

Initial release

2012

2010

1979

Current release

8.6, January 2023

V3, October 2020

License

Commercial or Open Source

commercial

Open Source

Elastic License

commercial

Restricted, free version available

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

ANSI C, C++

Server operating systems

hosted

All OS with a Java VM

Android
Linux

ARM, x86
Raspbian
Windows

Data scheme

yes

schema-free

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

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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.

yes

Secondary indexes

restricted

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

ANSI SQL queries

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP/JSON API

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

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

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

when using SQL

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.