DBMS > Cassandra vs. Google Cloud Datastore vs. JanusGraph vs. Microsoft Access vs. MySQL

System Properties Comparison Cassandra vs. Google Cloud Datastore vs. JanusGraph vs. Microsoft Access vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Vector DBMS

starting with release V5

Document store
Spatial DBMS

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

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

cassandra.apache.org

cloud.google.com/datastore

janusgraph.org

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

www.mysql.com

Technical documentation

cassandra.apache.org/doc/latest

cloud.google.com/datastore/docs

docs.janusgraph.org

developer.microsoft.com/en-us/access

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Google

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2008

2017

1992

1995

Current release

4.1.3, July 2023

0.6.3, February 2023

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++

C and C++

Server operating systems

BSD
Linux
OS X
Windows

hosted

Linux
OS X
Unix
Windows

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

restricted

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

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

SQL-like query language (GQL)

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

Proprietary protocol

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Clojure
Java
Python

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

using Google App Engine

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

Triggers

yes

Callbacks using the Google Apps Engine

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

Multi-source replication using Paxos

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

Atomicity and isolation are supported for single operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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

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.

yes

User concepts

Access control

Access rights for users can be defined per object

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

User authentification and security via Rexster Graph Server

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

Users with fine-grained authorization concept

no user groups or roles

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

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

Empowering On-Premises Deployments with Generative AI: Introducing Vector Search for a Self-Managed Modern Architecture
15 May 2024

Tips and Tricks for the DataStax Astra CLI
7 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.