DBMS > Amazon Redshift vs. Elasticsearch vs. FatDB vs. OrigoDB

System Properties Comparison Amazon Redshift vs. Elasticsearch vs. FatDB vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Search engine

Document store
Key-value store

Document store
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

aws.amazon.com/redshift

www.elastic.co/elasticsearch

origodb.com

Technical documentation

docs.aws.amazon.com/redshift

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

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

Elastic

FatCloud

Robert Friberg et al

Initial release

2012

2010

2012

2009

under the name LiveDB

Current release

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

commercial

Open Source

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

Server operating systems

hosted

All OS with a Java VM

Windows

Linux
Windows

Data scheme

yes

schema-free

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

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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 be achieved using .NET

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

Via inetgration in SQL Server

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP/JSON API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

yes

Triggers

yes

by using the 'percolation' feature

yes

via applications

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

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

depending on model

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

Write ahead log

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

Can implement custom security layer via applications

Role based authorization

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.