DBMS > Amazon Redshift vs. CouchDB vs. Solr vs. TigerGraph

System Properties Comparison Amazon Redshift vs. CouchDB vs. Solr vs. TigerGraph

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 native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A widely used distributed, scalable search engine based on Apache Lucene

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

couchdb.apache.org

solr.apache.org

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

docs.couchdb.org/en/stable

solr.apache.org/resources.html

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Apache Software Foundation

Initial release

2012

2005

2006

2017

Current release

3.3.3, December 2023

9.6.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache Version 2

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

Erlang

Java

C++

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

yes

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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.

yes

Secondary indexes

restricted

yes

via views

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

Solr Parallel SQL Interface

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

Java plugins

yes

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

Transaction concepts

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

ACID

atomic operations within a single document possible

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

yes

Role-based access control

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.