DBMS > Google Cloud Datastore vs. HugeGraph vs. Microsoft Access vs. MySQL vs. SingleStore

System Properties Comparison Google Cloud Datastore vs. HugeGraph vs. Microsoft Access vs. MySQL vs. SingleStore

Editorial information provided by DB-Engines

Name

Description

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

A fast-speed and highly-scalable Graph DBMS

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Document store

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	5.60
Rank	#62	Overall
	#35	Relational DBMS

Website

cloud.google.com/datastore

github.com/hugegraph
hugegraph.apache.org

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

www.mysql.com

www.singlestore.com

Technical documentation

cloud.google.com/datastore/docs

hugegraph.apache.org/docs

developer.microsoft.com/en-us/access

dev.mysql.com/doc

docs.singlestore.com

Developer

Google

Baidu

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

SingleStore Inc.

Initial release

2008

2018

1992

1995

2013

Current release

0.9

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

8.5, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free developer edition 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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

Java

C++

C and C++

C++, Go

Server operating systems

hosted

Linux
macOS
Unix

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Linux

64 bit version required

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

also supports composite index and range index

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

but not compliant to any SQL standard

yes

with proprietary extensions

yes

but no triggers and foreign keys

APIs and other access methods

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

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

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

Groovy
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

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

asynchronous Gremlin script jobs

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

yes

Triggers

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

yes

depending on used storage backend, e.g. Cassandra and HBase

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Multi-source replication
Source-replica replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

via hugegraph-spark

can define user-defined aggregate functions for map-reduce-style calculations

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

edges in graph

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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)

Users, roles and permissions

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

Users with fine-grained authorization concept

no user groups or roles

Fine grained access control via users, groups and roles

More information provided by the system vendor

Specific characteristics

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» 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.