DBMS > Google Cloud Datastore vs. Kyligence Enterprise vs. SAP SQL Anywhere vs. SingleStore vs. Snowflake

System Properties Comparison Google Cloud Datastore vs. Kyligence Enterprise vs. SAP SQL Anywhere vs. SingleStore vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

A distributed analytics engine for big data, built on top of Apache Kylin

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.44
Rank	#259	Overall
	#118	Relational DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

cloud.google.com/datastore

kyligence.io/kyligence-enterprise

www.sap.com/products/technology-platform/sql-anywhere.html

www.singlestore.com

www.snowflake.com

Technical documentation

cloud.google.com/datastore/docs

help.sap.com/docs/SAP_SQL_Anywhere

docs.singlestore.com

docs.snowflake.net/manuals/index.html

Developer

Google

Kyligence, Inc.

SAP

formerly Sybase

SingleStore Inc.

Snowflake Computing Inc.

Initial release

2008

2016

1992

2013

2014

Current release

17, July 2015

8.5, January 2024

License

Commercial or Open Source

commercial

free developer edition available

commercial

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.

Implementation language

Java

C++, Go

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

64 bit version required

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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 SQL for queries (using Apache Calcite)

yes

but no triggers and foreign keys

yes

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

yes, in C/C++, Java, .Net or Perl

yes

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

hash partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Database mirroring

Source-replica replication

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

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

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)

fine grained access rights according to SQL-standard

Fine grained access control via users, groups and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.