DBMS > EXASOL vs. Hazelcast vs. Snowflake vs. Teradata vs. Yaacomo

System Properties Comparison EXASOL vs. Hazelcast vs. Snowflake vs. Teradata vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A widely adopted in-memory data grid

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

A hybrid cloud data analytics software platform (Teradata Vantage)

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

yaacomo.com

Technical documentation

www.exasol.com/resources

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

docs.teradata.com

Developer

Exasol

Hazelcast

Snowflake Computing Inc.

Teradata

Q2WEB GmbH

Initial release

2000

2008

2014

1984

2009

Current release

5.3.6, November 2023

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

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

Server operating systems

All OS with a Java VM

hosted

hosted
Linux

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL 2016 + extensions

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Events

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Hashing

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

Multi-source replication
Source-replica replication

Source-replica replication

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

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

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

fine grained access rights according to SQL-standard

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.