DBMS > Databend vs. Google Cloud Datastore vs. InfinityDB vs. Snowflake

System Properties Comparison Databend vs. Google Cloud Datastore vs. InfinityDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

A Java embedded Key-Value Store which extends the Java Map interface

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

Primary database model

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

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/datafuselabs/databend
www.databend.com

cloud.google.com/datastore

boilerbay.com

www.snowflake.com

Technical documentation

docs.databend.com

cloud.google.com/datastore/docs

boilerbay.com/infinitydb/manual

docs.snowflake.net/manuals/index.html

Developer

Databend Labs

Google

Boiler Bay Inc.

Snowflake Computing Inc.

Initial release

2021

2008

2002

2014

Current release

1.0.59, April 2023

4.0

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Rust

Java

Server operating systems

hosted
Linux
macOS

hosted

All OS with a Java VM

hosted

Data scheme

yes

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

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

Typing

predefined data types such as float or date

yes

yes, details here

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

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

Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

none

yes

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

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

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

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.

User concepts

Access control

Users with fine-grained authorization concept, user roles

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.