DBMS > Amazon Redshift vs. Infobright vs. Lovefield vs. Sphinx

System Properties Comparison Amazon Redshift vs. Infobright vs. Lovefield vs. Sphinx

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

Embeddable relational database for web apps written in pure JavaScript

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Search engine

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

ignitetech.com/softwarelibrary/infobrightdb

google.github.io/lovefield

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

github.com/google/lovefield/blob/master/docs/spec_index.md

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Ignite Technologies Inc.; formerly InfoBright Inc.

Google

Sphinx Technologies Inc.

Initial release

2012

2005

2014

2001

Current release

2.1.12, February 2017

3.5.1, February 2023

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 2.0

Open Source

GPL version 2, commercial licence 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

JavaScript

C++

Server operating systems

hosted

Linux
Windows

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

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

restricted

Knowledge Grid Technology used instead

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

via JavaScript builder pattern

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

Proprietary protocol

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

JavaScript

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.