DBMS > Hazelcast vs. Interbase vs. mSQL vs. Snowflake

System Properties Comparison Hazelcast vs. Interbase vs. mSQL vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

Light-weight proven RDBMS

originally from Borland

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

Primary database model

Key-value store

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	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

hazelcast.com

www.embarcadero.com/products/interbase

hughestech.com.au/products/msql

www.snowflake.com

Technical documentation

hazelcast.org/imdg/docs

docs.embarcadero.com/products/interbase

docs.snowflake.net/manuals/index.html

Developer

Hazelcast

Embarcadero

Hughes Technologies

Snowflake Computing Inc.

Initial release

2008

1984

1994

2014

Current release

5.3.6, November 2023

InterBase 2020, December 2019

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

free licenses can be provided

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

Android
iOS
Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

hosted

Data scheme

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

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Interbase procedure and trigger language

user defined functions

Triggers

yes

Events

yes

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

Interbase Change Views

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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

Role-based access control

fine grained access rights according to SQL-standard

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.