DBMS > Amazon Redshift vs. EsgynDB vs. H2GIS vs. Kinetica vs. Solr

System Properties Comparison Amazon Redshift vs. EsgynDB vs. H2GIS vs. Kinetica vs. Solr

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Spatial extension of H2

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Secondary database models

Relational DBMS

Spatial DBMS
Time Series DBMS

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

www.h2gis.org/docs/home

docs.kinetica.com

solr.apache.org/resources.html

Developer

Amazon (based on PostgreSQL)

Esgyn

CNRS

Kinetica

Apache Software Foundation

Initial release

2012

2015

2013

2012

2006

Current release

7.1, August 2021

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

commercial

Open Source

Apache 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

C++, Java

Java

C, C++

Java

Server operating systems

hosted

Linux

All OS with a Java VM

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

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like DML and DDL statements

Solr Parallel SQL Interface

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

Java

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

yes

based on H2

user defined functions

Java plugins

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

yes

based on H2

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual 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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

GPU vRAM or System RAM

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

based on H2

Access rights for users and roles on table level

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.