DBMS > Ignite vs. Memcached vs. SQLite vs. Yanza

System Properties Comparison Ignite vs. Memcached vs. SQLite vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded 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.

In-memory key-value store, originally intended for caching

Widely used embeddable, in-process RDBMS

Time Series DBMS for IoT Applications

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Time Series 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	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

ignite.apache.org

www.memcached.org

www.sqlite.org

yanza.com

Technical documentation

apacheignite.readme.io/docs

github.com/memcached/memcached/wiki

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Dwayne Richard Hipp

Yanza

Initial release

2015

2003

2000

2015

Current release

Apache Ignite 2.6

1.6.25, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD license

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java, .Net

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Unix
Windows

server-less

Windows

Data scheme

yes

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.

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

SQL-92 is not fully supported

APIs and other access methods

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

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

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

Triggers

yes (cache interceptors and events)

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Repcached, a Memcached patch, provides this functionallity

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

Security Hooks for custom implementations

yes

using SASL (Simple Authentication and Security Layer) protocol

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.