DBMS > Heroic vs. JaguarDB vs. Netezza vs. Snowflake vs. Sqrrl

System Properties Comparison Heroic vs. JaguarDB vs. Netezza vs. Snowflake vs. Sqrrl

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Performant, highly scalable DBMS for AI and IoT applications

Data warehouse and analytics appliance part of IBM PureSystems

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Time Series DBMS

Key-value store
Vector DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/spotify/heroic

www.jaguardb.com

www.ibm.com/products/netezza

www.snowflake.com

sqrrl.com

Technical documentation

spotify.github.io/heroic

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Spotify

DataJaguar, Inc.

IBM

Snowflake Computing Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

2014

2015

2000

2014

2012

Current release

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL V3.0

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++

the server part. Clients available in other languages

Java

Server operating systems

Linux

included in appliance

hosted

Linux

Data scheme

schema-free

yes

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

schema-free

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
ODBC

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

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

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

yes

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

Eventual Consistency
Immediate Consistency

Eventual Consistency

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

ACID

Atomic updates per row, document, or graph entity

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.

User concepts

Access control

rights management via user accounts

Users with fine-grained authorization concept

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

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.