DBMS > Amazon Redshift vs. Geode vs. Infobright vs. LokiJS

System Properties Comparison Amazon Redshift vs. Geode vs. Infobright vs. LokiJS

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

In-memory JavaScript DBMS

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Website

aws.amazon.com/redshift

geode.apache.org

ignitetech.com/softwarelibrary/infobrightdb

github.com/techfort/LokiJS

Technical documentation

docs.aws.amazon.com/redshift

geode.apache.org/docs

techfort.github.io/LokiJS

Developer

Amazon (based on PostgreSQL)

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2012

2002

2005

2014

Current release

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

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

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

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

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

Data scheme

yes

schema-free

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

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

View functions in JavaScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

none

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

none

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

yes, on a single node

ACID

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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 per client and object definable

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.