DBMS > Amazon Redshift vs. BoltDB vs. Ignite vs. KairosDB vs. PostGIS

System Properties Comparison Amazon Redshift vs. BoltDB vs. Ignite vs. KairosDB vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Distributed Time Series DBMS based on Cassandra or H2

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

Key-value store

Key-value store
Relational DBMS

Time Series DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

aws.amazon.com/redshift

github.com/boltdb/bolt

ignite.apache.org

github.com/kairosdb/kairosdb

postgis.net

Technical documentation

docs.aws.amazon.com/redshift

apacheignite.readme.io/docs

kairosdb.github.io

postgis.net/documentation

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Initial release

2012

2013

2015

2013

2005

Current release

Apache Ignite 2.6

1.2.2, November 2018

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPL v2.0

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

C++, Java, .Net

Java

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java
PHP
Python
Ruby
Scala

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes (replicated cache)

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

Security Hooks for custom implementations

simple password-based access control

yes

based on PostgreSQL

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.