DBMS > EXASOL vs. Hazelcast vs. Realm vs. searchxml vs. Snowflake

System Properties Comparison EXASOL vs. Hazelcast vs. Realm vs. searchxml vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A widely adopted in-memory data grid

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

DBMS for structured and unstructured content wrapped with an application server

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Key-value store

Document store

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.exasol.com

hazelcast.com

realm.io

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

www.exasol.com/resources

hazelcast.org/imdg/docs

realm.io/docs

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

Exasol

Hazelcast

Realm, acquired by MongoDB in May 2019

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2000

2008

2014

2015

2014

Current release

5.3.6, November 2023

1.0

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

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

All OS with a Java VM

Android
Backend: server-less
iOS
Windows

Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

runs within the applications so server-side scripts are unnecessary

yes

on the application server

user defined functions

Triggers

yes

Events

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

none

yes

sychronisation to multiple collections

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

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

ACID

multiple readers, single writer

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

In-Memory realm

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Role-based access control

yes

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.