DBMS > Machbase Neo vs. Microsoft Azure Table Storage vs. SQLite vs. XTDB vs. YottaDB

System Properties Comparison Machbase Neo vs. Microsoft Azure Table Storage vs. SQLite vs. XTDB vs. YottaDB

Editorial information provided by DB-Engines

Name

Description

TimeSeries DBMS for AIoT and BigData

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

Widely used embeddable, in-process RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

machbase.com

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

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

yottadb.com

Technical documentation

machbase.com/dbms

www.sqlite.org/docs.html

www.xtdb.com/docs

yottadb.com/resources/documentation

Developer

Machbase

Microsoft

Dwayne Richard Hipp

Juxt Ltd.

YottaDB, LLC

Initial release

2013

2012

2000

2019

2001

Current release

V8.0, August 2023

3.45.3 (15 April 2024), April 2024

1.19, September 2021

License

Commercial or Open Source

commercial

free test version available

commercial

Open Source

Public Domain

Open Source

MIT License

Open Source

AGPL 3.0

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

Clojure

Server operating systems

Linux
macOS
Windows

hosted

server-less

All OS with a Java 8 (and higher) VM
Linux

Docker
Linux

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.

yes, extensible-data-notation format

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

by using the Octo plugin

APIs and other access methods

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

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP REST
JDBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
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

Clojure
Java

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

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

none

yes, each node contains all data

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

optimistic locking

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

simple password-based access control

Access rights based on private key authentication or shared access signatures

Users and groups based on OS-security mechanisms

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.