DBMS > Altibase vs. Google Cloud Datastore vs. Microsoft Access vs. MySQL vs. ScyllaDB

System Properties Comparison Altibase vs. Google Cloud Datastore vs. Microsoft Access vs. MySQL vs. ScyllaDB

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

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

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

Cassandra and DynamoDB compatible wide column store

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Wide column store

Secondary database models

Document store
Spatial DBMS

Key-value store

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

Score	1.07
Rank	#186	Overall
	#87	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Website

altibase.com

cloud.google.com/datastore

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

www.mysql.com

www.scylladb.com

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

cloud.google.com/datastore/docs

developer.microsoft.com/en-us/access

dev.mysql.com/doc

docs.scylladb.com

Developer

Altibase

Google

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

ScyllaDB

Initial release

1999

2008

1992

1995

2015

Current release

v7.3, 2023, August 2023

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

ScyllaDB Open Source 5.4.1, January 2024

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Open Source (AGPL), commercial license 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.

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

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C++

C and C++

C++

Server operating systems

AIX
HP-UX
Linux

hosted

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

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

yes

cluster global secondary indices

SQL

Support of SQL

ANSI SQL-92

SQL-like query language (GQL)

yes

but not compliant to any SQL standard

yes

with proprietary extensions

SQL-like DML and DDL statements (CQL)

APIs and other access methods

JDBC
ODBC
Proprietary protocol

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

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

Supported programming languages

C
C++
Java

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

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

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Server-side scripts

Stored procedures

stored procedures and stored functions

using Google App Engine

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

yes, Lua

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

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

selectable replication factor

Representation of geographical distribution of servers is possible

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

Atomicity and isolation are supported for single operations

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

in-memory tables

User concepts

Access control

fine grained access rights according to SQL-standard

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

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.