DBMS > EXASOL vs. Hazelcast vs. Manticore Search vs. Snowflake

System Properties Comparison EXASOL vs. Hazelcast vs. Manticore Search vs. Snowflake

Please select another system to include it in the comparison.

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

Multi-storage database for search, including full-text search.

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

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Time Series DBMS

using the Manticore Columnar Library

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	0.22
Rank	#312	Overall
	#21	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

www.exasol.com/resources

hazelcast.org/imdg/docs

manual.manticoresearch.com

docs.snowflake.net/manuals/index.html

Developer

Exasol

Hazelcast

Manticore Software

Snowflake Computing Inc.

Initial release

2000

2008

2017

2014

Current release

5.3.6, November 2023

6.0, February 2023

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

All OS with a Java VM

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

yes

schema-free

Fixed schema

yes

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

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Synchronous replication based on Galera library

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

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

Role-based access control

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.