DBMS > Google Cloud Datastore vs. Snowflake vs. Sphinx vs. SQream DB

System Properties Comparison Google Cloud Datastore vs. Snowflake vs. Sphinx vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

cloud.google.com/datastore

www.snowflake.com

sphinxsearch.com

sqream.com

Technical documentation

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

docs.sqream.com

Developer

Google

Snowflake Computing Inc.

Sphinx Technologies Inc.

SQream Technologies

Initial release

2008

2014

2001

2017

Current release

3.5.1, February 2023

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence 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

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes, details here

yes

yes, ANSI Standard SQL Types

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

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

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

CLI Client
JDBC
ODBC

Proprietary protocol

.Net
JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

user defined functions in Python

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

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

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

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.