DBMS > Google Cloud Datastore vs. Milvus vs. Snowflake vs. Spark SQL vs. Transbase

System Properties Comparison Google Cloud Datastore vs. Milvus vs. Snowflake vs. Spark SQL vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

A DBMS designed for efficient storage of vector data and vector similarity searches

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Vector DBMS

Relational DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.31
Rank	#113	Overall
	#3	Vector DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

cloud.google.com/datastore

milvus.io

www.snowflake.com

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/datastore/docs

milvus.io/docs/overview.md

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

Google

Snowflake Computing Inc.

Apache Software Foundation

Transaction Software GmbH

Initial release

2008

2019

2014

1987

Current release

2.3.4, January 2024

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

commercial

free development license

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.

Zilliz Cloud – Cloud-native service for Milvus

Implementation language

C++, Go

Scala

C and C++

Server operating systems

hosted

Linux
macOS

10.14 or later
Windows

with WSL 2 enabled

hosted

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

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

Vector, Numeric and String

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)

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

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

RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C++
Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

yes

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

Source-replica replication

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.

Bounded Staleness
Eventual Consistency
Immediate Consistency
Session Consistency
Tunable Consistency

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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)

Role based access control and fine grained access rights

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

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Milvus is an open-source and cloud-native vector database built for production-ready...
» more

Competitive advantages

Highly available, versatile, and robust with millisecond latency. Supports batch...
» more

Typical application scenarios

RAG: retrieval augmented generation Video media : video understanding, video deduplication....
» more

Key customers

Milvus is trusted by thousands of enterprises, including PayPal, eBay, IKEA, LINE,...
» more

Market metrics

As of January 2024, 25k+ GitHub stars 10M+ downloads and installations 3k+ enterprise...
» more

Licensing and pricing models

Milvus was released under the open-source Apache License 2.0 in October 2019. Fully-managed...
» 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.