DBMS > Ignite vs. Linter vs. RocksDB vs. SiteWhere vs. Sqrrl

System Properties Comparison Ignite vs. Linter vs. RocksDB vs. SiteWhere 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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

RDBMS for high security requirements

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

M2M integration platform for persisting/querying time series data

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key-value store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

ignite.apache.org

linter.ru

rocksdb.org

github.com/sitewhere/sitewhere

sqrrl.com

Technical documentation

apacheignite.readme.io/docs

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation

relex.ru

Facebook, Inc.

SiteWhere

Amazon

originally Sqrrl Data, Inc.

Initial release

2015

1990

2013

2010

2012

Current release

Apache Ignite 2.6

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

Common Public Attribution License Version 1.0

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

C++, Java, .Net

C and C++

C++

Java

Server operating systems

Linux
OS X
Solaris
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

predefined scheme

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

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

C++ API
Java API

HTTP REST

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Go
Java
Perl
Python
Ruby

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 (compute grid and cache interceptors can be used instead)

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

based on HBase

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

yes

selectable replication factor

based on HBase

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

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.

yes

User concepts

Access control

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.