DBMS > Google Cloud Datastore vs. Ignite vs. Microsoft Access vs. MySQL vs. Vitess

System Properties Comparison Google Cloud Datastore vs. Ignite vs. Microsoft Access vs. MySQL vs. Vitess

Editorial information provided by DB-Engines

Name

Description

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

cloud.google.com/datastore

ignite.apache.org

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

www.mysql.com

vitess.io

Technical documentation

cloud.google.com/datastore/docs

apacheignite.readme.io/docs

developer.microsoft.com/en-us/access

dev.mysql.com/doc

vitess.io/docs

Developer

Google

Apache Software Foundation

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

The Linux Foundation, PlanetScale

Initial release

2008

2015

1992

1995

2013

Current release

Apache Ignite 2.6

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0, commercial licenses 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.

Implementation language

C++, Java, .Net

C++

C and C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL-like query language (GQL)

ANSI-99 for query and DML statements, subset of DDL

yes

but not compliant to any SQL standard

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

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 (compute grid and cache interceptors can be used instead)

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

yes

proprietary syntax

Triggers

Callbacks using the Google Apps Engine

yes (cache interceptors and events)

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

Multi-source replication using Paxos

yes (replicated cache)

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

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

Security Hooks for custom implementations

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

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

no user groups or roles

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.