DBMS > BigchainDB vs. Cassandra vs. Microsoft Access vs. SiteWhere

System Properties Comparison BigchainDB vs. Cassandra vs. Microsoft Access vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

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.)

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Vector DBMS

starting with release V5

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	98.83
Rank	#12	Overall
	#1	Wide column stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

www.bigchaindb.com

cassandra.apache.org

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

github.com/sitewhere/sitewhere

Technical documentation

bigchaindb.readthedocs.io/en/latest

cassandra.apache.org/doc/latest

developer.microsoft.com/en-us/access

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Microsoft

SiteWhere

Initial release

2016

2008

1992

2010

Current release

4.1.3, July 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

Open Source

Common Public Attribution License Version 1.0

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.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Python

Java

C++

Java

Server operating systems

Linux

BSD
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Windows

Data scheme

schema-free

yes

predefined scheme

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

restricted

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

yes

but not compliant to any SQL standard

APIs and other access methods

CLI Client
RESTful HTTP API

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomicity and isolation are supported for single operations

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

but no files for transaction logging

yes

In-memory capabilities

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

User concepts

Access control

yes

Access rights for users can be defined per object

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

Users with fine-grained authorization concept

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

News

An Introduction to Phil Nash, Developer Relations
3 June 2024

Focus on Creativity, Not Clusters: DataStax Mission Control in Action!
30 May 2024

How Concide Built its Chat Platform with Enhanced Document Management for Legal Tech Professionals
23 May 2024

Astra Vectorize: Generate Vector Embeddings with 1 Line of Code
22 May 2024

GitHub Copilot + DataStax Astra DB: Build GenAI Apps 100x Faster
21 May 2024

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.