DBMS > ArangoDB vs. Google Cloud Datastore vs. Snowflake vs. Yanza

System Properties Comparison ArangoDB vs. Google Cloud Datastore vs. Snowflake vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Native multi-model DBMS for graph, document, key/value and search. All in one engine and accessible with one query language.

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

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

Time Series DBMS for IoT Applications

Primary database model

Document store
Graph DBMS
Key-value store
Search engine

Document store

Relational DBMS

Time Series DBMS

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

Score	3.77
Rank	#87	Overall
	#15	Document stores
	#5	Graph DBMS
	#12	Key-value stores
	#10	Search engines

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

arangodb.com

cloud.google.com/datastore

www.snowflake.com

yanza.com

Technical documentation

docs.arangodb.com

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

Social network pages

Developer

ArangoDB Inc.

Google

Snowflake Computing Inc.

Yanza

Initial release

2012

2008

2014

2015

Current release

3.11.5, November 2023

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial license (Enterprise) available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

ArangoDB Cloud –The Managed Cloud Service of ArangoDB. Provides fully managed, and monitored cluster deployments of any size, with enterprise-grade security. Get started for free and continue for as little as $0,21/hour.

Implementation language

C++

Server operating systems

Linux
OS X
Windows

hosted

Windows

Data scheme

schema-free

automatically recognizes schema within a collection

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

string, double, boolean, list, hash

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)

yes

APIs and other access methods

AQL
Foxx Framework
Graph API (Gremlin)
GraphQL query language
HTTP API
Java & SpringData
JSON style queries
VelocyPack/VelocyStream

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

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

C#
C++
Clojure
Elixir
Go
Java
JavaScript (Node.js)
PHP
Python
R
Rust

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

JavaScript (Node.js)
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

JavaScript

using Google App Engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

since version 2.0

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with configurable replication factor

Multi-source replication using Paxos

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can be done with stored procedures in JavaScript

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

configurable per collection or per write
Immediate Consistency
OneShard (highly available, fault-tolerant deployment mode with ACID semantics)

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

relationships in graphs

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

In-memory capabilities

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

User concepts

Access control

yes

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

Specific characteristics

Graph and Beyond. With more than 11,000 stargazers on GitHub, ArangoDB is the leading...
» more

Competitive advantages

Consolidation: As a native multi-model database, can be used as a full blown document...
» more

Typical application scenarios

Native multi-model in ArangoDB is being used for a broad range of projects across...
» more

Key customers

Cisco, Barclays, Refinitive, Siemens Mentor, Kabbage, Liaison, Douglas, MakeMyTrip,...
» more

Market metrics

ArangoDB is the leading native multi-model database with over 11,000 stargazers on...
» more

Licensing and pricing models

Very permissive Apache 2 License for Community Edition & commercial licenses are...
» 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.