DBMS > Google BigQuery vs. Machbase Neo vs. MarkLogic vs. XTDB

System Properties Comparison Google BigQuery vs. Machbase Neo vs. MarkLogic vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

TimeSeries DBMS for AIoT and BigData

Operational and transactional Enterprise NoSQL database

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

Primary database model

Relational DBMS

Time Series DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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.11
Rank	#343	Overall
	#46	Document stores

Website

cloud.google.com/bigquery

machbase.com

www.marklogic.com

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

Technical documentation

cloud.google.com/bigquery/docs

machbase.com/dbms

docs.marklogic.com

www.xtdb.com/docs

Developer

Google

Machbase

MarkLogic Corp.

Juxt Ltd.

Initial release

2010

2013

2001

2019

Current release

V8.0, August 2023

11.0, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

free test version available

commercial

restricted free version is available

Open Source

MIT License

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

Clojure

Server operating systems

hosted

Linux
macOS
Windows

Linux
OS X
Windows

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

Data scheme

yes

schema-free

Schema can be enforced

schema-free

Typing

predefined data types such as float or date

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL92

limited SQL, making use of Apache Calcite

APIs and other access methods

RESTful HTTP/JSON API

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

HTTP REST
JDBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

via XQuery or JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

yes, each node contains all data

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

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

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

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

simple password-based access control

Role-based access control at the document and subdocument levels

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.