DBMS > BigchainDB vs. Microsoft Access vs. SAP HANA vs. Splice Machine vs. Titan

System Properties Comparison BigchainDB vs. Microsoft Access vs. SAP HANA vs. Splice Machine vs. Titan

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

In-memory, column based data store. Available as appliance or cloud service

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Document store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

www.bigchaindb.com

www.microsoft.com/en-us/microsoft-365/access

www.sap.com/products/hana.html

splicemachine.com

github.com/thinkaurelius/titan

Technical documentation

bigchaindb.readthedocs.io/en/latest

developer.microsoft.com/en-us/access

help.sap.com/hana

splicemachine.com/how-it-works

github.com/thinkaurelius/titan/wiki

Developer

Microsoft

SAP

Splice Machine

Aurelius, owned by DataStax

Initial release

2016

1992

2010

2014

2012

Current release

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

3.1, March 2021

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Bundled with Microsoft Office

commercial

Open Source

AGPL 3.0, commercial license available

Open Source

Apache license, version 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Python

C++

Java

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

SQLScript, R

yes

Java

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

but no files for transaction logging

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

yes

a simple user-level security was built in till version Access 2003

yes

Access rights for users, groups and roles according to SQL-standard

User authentification and security via Rexster Graph Server

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.