DBMS > Hazelcast vs. Ingres vs. SQLite vs. Sqrrl

System Properties Comparison Hazelcast vs. Ingres vs. SQLite vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

A widely adopted in-memory data grid

Well established RDBMS

Widely used embeddable, in-process RDBMS

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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.97
Rank	#57	Overall
	#6	Key-value stores

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

www.actian.com/databases/ingres

www.sqlite.org

sqrrl.com

Technical documentation

hazelcast.org/imdg/docs

docs.actian.com/ingres

www.sqlite.org/docs.html

Developer

Hazelcast

Actian Corporation

Dwayne Richard Hipp

Amazon

originally Sqrrl Data, Inc.

Initial release

2008

1974

originally developed at University Berkely in early 1970s

2000

2012

Current release

5.3.6, November 2023

11.2, May 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Public Domain

commercial

Cloud-based only

Only available as a cloud service

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

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

none

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Ingres Replicator

none

selectable replication factor

making use of Hadoop

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

via file-system locks

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.