DBMS > Amazon Aurora vs. Amazon Redshift vs. Solr vs. XTDB

System Properties Comparison Amazon Aurora vs. Amazon Redshift vs. Solr vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Large scale data warehouse service for use with business intelligence tools

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Search engine

Document store

Secondary database models

Document store

Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/rds/aurora

aws.amazon.com/redshift

solr.apache.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.aws.amazon.com/redshift

solr.apache.org/resources.html

www.xtdb.com/docs

Developer

Amazon

Amazon (based on PostgreSQL)

Apache Software Foundation

Juxt Ltd.

Initial release

2015

2012

2006

2019

Current release

9.6.0, April 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

MIT License

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

Server operating systems

hosted

All OS with a Java VM

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

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

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

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes, extensible-data-notation format

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

yes

restricted

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Solr Parallel SQL Interface

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

Java API
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC

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

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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

Transaction concepts

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

ACID

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

yes

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.