DBMS > Apache IoTDB vs. Ignite vs. Sadas Engine vs. SWC-DB

System Properties Comparison Apache IoTDB vs. Ignite vs. Sadas Engine vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A high performance, scalable Wide Column DBMS

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Wide column store

Secondary database models

Time Series DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

iotdb.apache.org

ignite.apache.org

www.sadasengine.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

apacheignite.readme.io/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Apache Software Foundation

SADAS s.r.l.

Alex Kashirin

Initial release

2018

2015

2006

2020

Current release

1.1.0, April 2023

Apache Ignite 2.6

8.0

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

free trial version available

Open Source

GPL V3

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

C++, Java, .Net

C++

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Solaris
Windows

AIX
Linux
Windows

Linux

Data scheme

yes

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

SQL-like query language

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

yes

SQL-like query language

APIs and other access methods

JDBC
Native API

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

JDBC
ODBC
Proprietary protocol

Proprietary protocol
Thrift

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

managed by 'Learn by Usage'

User concepts

Access control

yes

Security Hooks for custom implementations

Access rights for users, groups and roles 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

Benchmarking The Performance Impact To AMD Inception Mitigations
15 August 2023, Phoronix

IoTDB Provides Data Management for Industrial Edge IT
15 October 2020, The New Stack

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page