DBMS > Ignite vs. Machbase Neo vs. Microsoft Azure Table Storage vs. SAP Adaptive Server vs. SQLite

System Properties Comparison Ignite vs. Machbase Neo vs. Microsoft Azure Table Storage vs. SAP Adaptive Server vs. SQLite

Editorial information provided by DB-Engines

Name

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.

TimeSeries DBMS for AIoT and BigData

A Wide Column Store for rapid development using massive semi-structured datasets

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

ignite.apache.org

machbase.com

azure.microsoft.com/en-us/services/storage/tables

www.sap.com/products/technology-platform/sybase-ase.html

www.sqlite.org

Technical documentation

apacheignite.readme.io/docs

machbase.com/dbms

help.sap.com/docs/SAP_ASE

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Machbase

Microsoft

SAP, Sybase

Dwayne Richard Hipp

Initial release

2015

2013

2012

1987

2000

Current release

Apache Ignite 2.6

V8.0, August 2023

16.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free test version available

commercial

Open Source

Public Domain

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

C++, Java, .Net

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

hosted

AIX
HP-UX
Linux
Solaris
Unix
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

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

SQL-like query language

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Cobol
Java
Java
Perl
PHP
Python

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

Server-side scripts

Stored procedures

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

Java and Transact-SQL

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

selectable replication factor

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

volatile and lookup table

yes

User concepts

Access control

Security Hooks for custom implementations

simple password-based access control

Access rights based on private key authentication or shared access signatures

fine grained access rights 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.