DBMS > Amazon Redshift vs. Hazelcast vs. Percona Server for MongoDB vs. searchxml

System Properties Comparison Amazon Redshift vs. Hazelcast vs. Percona Server for MongoDB vs. searchxml

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

A widely adopted in-memory data grid

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

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Key-value store

Document store

Native XML DBMS
Search engine

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	0.50
Rank	#250	Overall
	#39	Document stores

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

aws.amazon.com/redshift

hazelcast.com

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

www.searchxml.net/category/products

Technical documentation

docs.aws.amazon.com/redshift

hazelcast.org/imdg/docs

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

www.searchxml.net/support/handouts

Developer

Amazon (based on PostgreSQL)

Hazelcast

Percona

informationpartners gmbh

Initial release

2012

2008

2015

Current release

5.3.6, November 2023

3.4.10-2.10, November 2017

1.0

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL Version 2

commercial

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

C++

Server operating systems

hosted

All OS with a Java VM

Linux

Windows

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.

yes

the object must implement a serialization strategy

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

proprietary protocol using JSON

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

JavaScript

yes

on the application server

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Immediate Consistency

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

one or two-phase-commit; repeatable reads; read commited

multiple readers, single writer

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

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

Access rights for users and roles

Domain, group and role-based access control at the document level and for application services

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.