DBMS > Amazon Redshift vs. Infobright vs. Solr vs. SQL.JS

System Properties Comparison Amazon Redshift vs. Infobright vs. Solr vs. SQL.JS

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Port of SQLite to JavaScript

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

aws.amazon.com/redshift

ignitetech.com/softwarelibrary/infobrightdb

solr.apache.org

sql.js.org

Technical documentation

docs.aws.amazon.com/redshift

solr.apache.org/resources.html

sql.js.org/documentation/index.html

Developer

Amazon (based on PostgreSQL)

Ignite Technologies Inc.; formerly InfoBright Inc.

Apache Software Foundation

Alon Zakai

enhancements implemented by others

Initial release

2012

2005

2006

2012

Current release

9.6.1, May 2024

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache Version 2

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

JavaScript

Server operating systems

hosted

Linux
Windows

All OS with a Java VM

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

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

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

Knowledge Grid Technology used instead

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Solr Parallel SQL Interface

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

Java API
RESTful HTTP/JSON API

JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

JavaScript

Server-side scripts

Stored procedures

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

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

none

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

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

except by serializing a db to a file

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

exploiting MySQL or PostgreSQL frontend capabilities

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.