DBMS > Machbase Neo vs. MarkLogic vs. Tkrzw vs. VoltDB

System Properties Comparison Machbase Neo vs. MarkLogic vs. Tkrzw vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

TimeSeries DBMS for AIoT and BigData

Operational and transactional Enterprise NoSQL database

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Time Series DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Relational DBMS

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

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

machbase.com/dbms

docs.marklogic.com

docs.voltdb.com

Developer

Machbase

MarkLogic Corp.

Mikio Hirabayashi

VoltDB Inc.

Initial release

2013

2001

2020

2010

Current release

V8.0, August 2023

11.0, December 2022

0.9.3, August 2020

11.3, April 2022

License

Commercial or Open Source

commercial

free test version available

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, C++

Server operating systems

Linux
macOS
Windows

Linux
OS X
Windows

Linux
macOS

Linux
OS X

for development

Data scheme

yes

schema-free

Schema can be enforced

schema-free

yes

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

yes

SQL92

yes

only a subset of SQL 99

APIs and other access methods

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

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

C++
Java
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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, with Range Indexes

yes

using specific database classes

User concepts

Access control

simple password-based access control

Role-based access control at the document and subdocument levels

Users and roles with access to stored procedures

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

“Luxembourg is a perfect target area”: Korean accelerator exec
27 October 2022, Delano.lu

provided by Google News

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
22 April 2024, Medium

ABN AMRO Moves Progress-Powered Credit Store App to Azure Cloud; Achieves 40% Faster Data Processing, Lower ...
12 March 2024, Yahoo Finance

Seven Quick Steps to Setting Up MarkLogic Server in Kubernetes
1 February 2024, release.nl

Progress's $355m move for MarkLogic sets the tone for 2023
4 January 2023, The Stack

Progress to acquire PE-backed data platform MarkLogic for $355m
4 January 2023, PE Hub

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Aims for Fast Big Data Development -- ADTmag
29 January 2015, ADT Magazine

provided by Google News

Share this page