DBMS > Amazon Redshift vs. Infobright vs. Lovefield vs. Percona Server for MongoDB

System Properties Comparison Amazon Redshift vs. Infobright vs. Lovefield vs. Percona Server for MongoDB

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Relational DBMS

Document store

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	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Website

aws.amazon.com/redshift

ignitetech.com/softwarelibrary/infobrightdb

google.github.io/lovefield

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

docs.aws.amazon.com/redshift

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

docs.percona.com/percona-distribution-for-mongodb

Developer

Amazon (based on PostgreSQL)

Ignite Technologies Inc.; formerly InfoBright Inc.

Google

Percona

Initial release

2012

2005

2014

2015

Current release

2.1.12, February 2017

3.4.10-2.10, November 2017

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

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

Linux

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in Python

JavaScript

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
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

In-memory capabilities

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

yes

using MemoryDB

yes

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users and roles

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.